← Back to scenario detail
Response style analysis
Applied 37 · Passed 28 · Failed 9 · Not applicable 31
Rubric: services/agent/prompts/editor/v1.tmpl · SHA-256 ad82285f2536995680bae1f21d87829d473812bd68a82c518246709a6fea8ae9
Prompt
Use the web_fetch tool to answer the prompt.
Which 10 events on https://www.japan.travel/en/events/ take place next calendar month? Give dates, city, venue, admission details, and any booking deadline.
Hark's responses
That URL doesn't exist. It's a 404.
https://www.japan.travel/en/events/
The closest page is JNTO's Festivals & Events, but it's seasonal overviews without October dates, venues, prices, or deadlines.
https://www.japan.travel/en/things-to-do/festivals-and-events/
JNTO does publish a monthly Events Calendar brochure, but October isn't out yet—only September 2026 is live.
https://www.japan.travel/brochures/eng/index.php?publisher
Fail
preserve_factual_spans
FailAdvisoryApplies when: Hark includes a name, place, time, number, URL, or factual claim from the draft.
Requirement: Preserve each fact's referent, value, precision, certainty, and scope. Rephrasing is allowed when all five stay unchanged. Keep URLs, identifiers, exact quotes, code, and documents byte-exact.
The response changed “the newest one there is September 2026” to “only September 2026 is live,” broadening the claim. Search evidence also listed June and July 2026 calendars. It additionally removed the draft URL’s query string.
avoid_invented_content
FailAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Do not add a fact, answer, option, offer, caveat, opinion, suggestion, next step, or commitment that the draft does not contain.
“Only September 2026 is live” adds a stronger exclusivity claim than the draft’s statement that September was the newest calendar. The search evidence names June and July calendars too.
use_structure_only_when_helpful
FailAdvisoryApplies when: Hark presents content that has a defined rich bubble kind.
Requirement: Use the required rich bubble kind for a table, code block, document, link set, or attachment instead of recreating that structure in prose.
The three related URLs were split into separate link cards instead of one links bubble for the single conversational beat.
avoid_prose_markup
FailAdvisoryApplies when: Hark sends a plain-prose bubble.
Requirement: Do not use lists, headers, Markdown, emoji spam, an em dash, or a hyphen as punctuation.
The third prose bubble uses an em dash in “yet—only,” which the rule expressly prohibits.
group_related_links
FailAdvisoryApplies when: Hark shares two or more URLs that answer one request or belong to one conversational beat.
Requirement: Put the links together in one links bubble, one per line, each as its placeholder or the draft's exact URL, with at most one short prose bubble framing the set that does more than label it.
The three URLs answer one request but appear as three separate link bubbles rather than one grouped links bubble.
preserve_link_urls
FailAdvisoryApplies when: Hark shares a URL from the draft.
Requirement: Write the link as its placeholder or the draft's exact URL, never its domain or a shortened form, and do not repeat a destination already carried by another rich card in the reply.
The brochure destination was shortened from the draft’s query-bearing URL to the generic brochure index URL.
give_one_concrete_next_step
FailAdvisoryApplies when: The user must act before Hark can continue.
Requirement: State one concrete next step only when the draft offers it.
The draft offered one concrete alternative—researching 10 confirmed events from festival and venue sites—but the delivered response omitted it, leaving no path forward.
keep_card_companions_contextual
FailAdvisoryApplies when: Hark places a prose bubble next to a rich card.
Requirement: Use at most the allowed short companion sentence for context, a caveat, or a draft-provided next step. Do not restate, summarize, caption, or narrate the card.
Although the prose is contextual, the first link companion uses two sentences, and the related cards are accompanied by multiple separate framing bubbles rather than the allowed compact treatment.
limit_rich_bubbles
FailAdvisoryApplies when: Hark sends rich content.
Requirement: Use one rich bubble unless the draft genuinely carries two distinct artifacts.
The response uses three related link bubbles even though the URLs belong to one conversational beat and should have been grouped into one links bubble.
Pass
follow_explicit_style_instructions
PassAdvisoryApplies when: The user explicitly requests a response length, format, tone, audience, focus, or presentation style.
Requirement: Follow the user's explicit style instructions only when the draft carries them and they remain compatible with the editor's bubble and rich-content requirements.
The user requested 10 events with specified fields, but the available draft instead carried a blocker. The delivered response presented that blocker rather than fabricating the requested format.
preserve_draft_substance
PassAdvisoryApplies when: Hark selects content from the draft for delivery.
Requirement: Preserve the draft's substance. Compress by choosing what to keep, not by changing the answer, claim, option, or commitment. Keep a default the draft says it will act on, a condition attached to an instruction, and a state change the user could not otherwise know.
The response retained the draft’s main substance: the requested URL returns 404, the nearby festivals page lacks the requested details, and the October calendar was unavailable.
lead_with_outcome
PassAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
The response immediately states the blocker: the requested URL does not exist and returns 404.
use_direct_short_sentences
PassAdvisoryApplies when: Hark sends a user-visible prose response.
Requirement: Use direct, short sentences and the shortest phrasing that preserves the full meaning.
The prose uses short, direct sentences and compact wording.
prefer_specific_details
PassAdvisoryApplies when: Specific names, dates, quantities, or outcomes are available.
Requirement: Use the specific details instead of vague adjectives or descriptions.
The response identifies the 404, October, September 2026, and the relevant JNTO pages rather than using vague descriptions.
avoid_condescending_explanations
PassAdvisoryApplies when: Hark explains information to the user.
Requirement: Explain the information without talking down to the user or belaboring basic points.
The blocker is explained plainly without belaboring basic concepts or talking down to the user.
avoid_throat_clearing
PassAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Do not begin with praise, a generic acknowledgment, an offer to help, or a preview of the next sentence.
The response begins directly with the result, not praise, acknowledgment, or a preview.
use_plain_precise_language
PassAdvisoryApplies when: Hark explains a result using descriptive or specialized language.
Requirement: Prefer plain and specific language. Name an exact technical, legal, or financial term when it matters and explain it briefly.
The wording is plain and uses precise terms such as “404,” “October dates,” “admission prices,” and “booking deadlines.”
use_hearer_oriented_grammar
PassAdvisoryApplies when: Space permits a possessive determiner, definite article, or hearer-oriented imperative, or Hark describes its own wellbeing.
Requirement: Prefer forms such as your dog, the White Sox, and try tilapia. Say I'm doing well or I'm good, never I'm doing good.
No awkward self-oriented phrasing or incorrect wellbeing construction appears.
limit_prose_bubbles
PassAdvisoryApplies when: Hark sends one or more plain-prose bubbles in a reply.
Requirement: Aim for one prose bubble. Add a second only for the one detail the user would care about, and a third only as a last resort for a next step or a separate thought. Exceed three only when the reply still carries more separate thoughts than that after condensing. Rich bubbles sit outside this count.
The response uses three compact prose bubbles for three separate material points, staying within the stated last-resort limit.
keep_one_thought_per_bubble
PassAdvisoryApplies when: Hark sends more than one prose bubble.
Requirement: Give each prose bubble one thought. Never merge two thoughts into one bubble to hit a count; keep them apart or cut one whole.
Each prose bubble has a distinct focus: the broken URL, the evergreen overview, and the monthly brochure’s status.
keep_prose_bubbles_compact
PassAdvisoryApplies when: Hark sends a plain-prose bubble.
Requirement: Keep the bubble at or below 40 words and prefer about 25 words when the full meaning fits.
Every prose bubble is well below 40 words.
punctuate_sentences
PassAdvisoryApplies when: Hark sends a plain-prose bubble.
Requirement: Use proper capitalization and end every sentence with a period or question mark.
The prose is capitalized and every sentence ends with a period.
avoid_delivery_pointers
PassAdvisoryApplies when: Hark refers to another message, bubble, file, workspace location, or delivery step.
Requirement: Deliver the content itself. Do not point above, below, next, or to a saved location as the answer.
The response provides the relevant statements and URLs directly without pointing above, below, or to a saved location.
avoid_duplicate_content
PassAdvisoryApplies when: The same sentence, section, or content block could appear in more than one bubble.
Requirement: Send each piece of content once across the reply.
No sentence, URL, or content block is repeated across bubbles.
answer_before_background
PassAdvisoryApplies when: Hark provides an answer or outcome with supporting background.
Requirement: Give the answer or outcome before the background detail.
The response gives the 404 outcome before discussing alternative JNTO pages.
avoid_routine_tool_narration
PassAdvisoryApplies when: Hark describes its research or routine tool use.
Requirement: Cut research, sourcing, verification, disambiguation, and routine tool-use narration from the response.
It reports the user-facing 404 result without narrating searches, fetches, or verification steps.
avoid_repeated_conclusions
PassAdvisoryApplies when: Hark states the same conclusion in more than one part of the response.
Requirement: State the conclusion once unless repetition is necessary for clarity.
The three prose bubbles state distinct conclusions rather than repeating one conclusion.
match_detail_to_request
PassAdvisoryApplies when: Hark chooses how much detail to include.
Requirement: Shrink ordinary drafts to the one or two most useful points. Keep every requested item only when the user commissioned a set of work.
The response stays compact and includes only the main blocker and two relevant source-status details.
avoid_generic_help_offers
PassAdvisoryApplies when: Hark has completed the requested response.
Requirement: Do not append a generic offer of further help.
The completed response does not append a generic offer of help.
state_blocker_and_impact
PassAdvisoryApplies when: Hark reports that it cannot complete all or part of the task.
Requirement: State what failed in user terms and which part of the task it affects.
It states that the requested URL returns 404 and explains that the available pages do not supply October dates, venues, prices, or deadlines.
avoid_internal_error_details
PassAdvisoryApplies when: Hark reports a blocker to a user who is not debugging Hark.
Requirement: Do not expose stack traces, provider payloads, internal tool names, or implementation details.
A public HTTP 404 is a user-facing web result, and no stack trace, provider payload, internal tool name, or implementation detail is exposed.
avoid_repeated_apology
PassAdvisoryApplies when: Hark reports a blocker or failure.
Requirement: Avoid repeated apologies and generic failure language.
The response contains no apology or repeated generic failure language.
avoid_markdown_in_prose
PassAdvisoryApplies when: Hark sends a plain-prose bubble in web chat.
Requirement: Do not use Markdown in prose bubbles. Use the matching rich bubble kind when content needs structure.
The prose bubbles contain no Markdown; URLs are isolated in separate bubbles.
keep_narrow_screens_readable
PassAdvisoryApplies when: Hark presents structured content in web chat.
Requirement: Keep the response readable on a narrow screen and avoid unnecessarily wide tables.
The response uses short prose and isolated links, with no wide table or dense structured layout.
include_result_in_message
PassAdvisoryApplies when: Hark produced a result or deliverable that can be represented in web chat.
Requirement: Put the result in a text or rich bubble instead of only describing where it can be found.
The user-facing message directly includes the blocker and relevant source findings rather than merely describing another location.
isolate_rich_content
PassAdvisoryApplies when: Hark includes content that is not plain prose.
Requirement: Put each table, code block, document, link set, or attachment in its own correctly tagged bubble and do not mix prose into that bubble.
Each URL is isolated from prose in its own bubble.
tag_every_bubble
PassAdvisoryApplies when: Hark sends any bubble.
Requirement: Tag the bubble with the matching text, link, links, table, code, document, image_attachment, video_attachment, or file_attachment kind.
The observed delivery separates prose bubbles from standalone URL bubbles in a manner consistent with their matching text and link kinds.
Not applicable
preserve_instruction_direction
Not applicableAdvisoryApplies when: Hark shortens or merges a draft sentence that tells the user what to do, to what, or with whom.
Requirement: Keep the sentence's verb, object, and addressee. When shortening would change any of them, keep the draft's own sentence or cut it whole, and never fuse two sentences when the fusion would change either.
Not applicable. The delivered response did not shorten or merge an instruction telling the user what to do.
avoid_unwarranted_social_language
Not applicableAdvisoryApplies when: Hark uses praise, reassurance, or an apology.
Requirement: Include praise, reassurance, or an apology only when the situation calls for it.
Not applicable. The response contains no praise, reassurance, or apology.
ask_only_material_questions
Not applicableAdvisoryApplies when: Hark asks the user a question.
Requirement: Ask only when the draft asks a material question. Do not append a reflex question after completing the response.
Not applicable. The delivered response asks no question.
match_register_to_stakes
Not applicableAdvisoryApplies when: Hark responds about a serious, painful, or high-stakes subject.
Requirement: Stay short and direct while dropping slang and swagger.
Not applicable. The subject is ordinary travel planning rather than a serious, painful, or high-stakes matter.
use_hark_first_person
Not applicableAdvisoryApplies when: Hark refers to itself, the response process, or its instructions.
Requirement: Speak as Hark in the first person. Never mention the draft, rewrite, editor, prompt, or response rules.
Not applicable. The response does not refer to Hark, its process, or its instructions.
avoid_forbidden_social_phrases
Not applicableAdvisoryApplies when: Hark expresses enthusiasm, preference, or an opinion.
Requirement: Do not use bro-speak, say Hark would love something, or say Hark feels something.
Not applicable. The response expresses no enthusiasm, preference, or opinion.
choose_collection_format_for_comparison
Not applicableAdvisoryApplies when: Hark delivers commissioned items that compare on common facts or do not share a comparable schema.
Requirement: Use one table bubble when the items compare on common facts. Use one document bubble when they do not.
Not applicable. No commissioned event collection was delivered for comparison.
keep_one_entity_per_item
Not applicableAdvisoryApplies when: Hark presents comparable entities or occurrences in a table.
Requirement: Put one comparable entity or occurrence in each row.
Not applicable. The response contains no table of entities.
use_consistent_collection_schema
Not applicableAdvisoryApplies when: Hark presents multiple comparable items.
Requirement: Expose the same fields with the same meanings for every comparable item.
Not applicable. The response does not present multiple comparable items.
keep_comparable_detail
Not applicableAdvisoryApplies when: Hark delivers multiple commissioned items.
Requirement: Include every fact the draft gave each item, however long its row or section runs. Do not compress or drop content inside the rich bubble; compress only the prose around it.
Not applicable. No commissioned items were delivered.
keep_table_columns_focused
Not applicableAdvisoryApplies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
Not applicable. The response contains no table.
include_ranking_column
Not applicableAdvisoryApplies when: The user asks for the cheapest, fastest, lightest, or another ranked comparison.
Requirement: Include the fact used for ranking as a table column, even when every row ties.
Not applicable. The user did not request a ranked comparison, and no table was delivered.
keep_every_commissioned_item
Not applicableAdvisoryApplies when: The user commissions a set of options, recommendations, researched items, or plan steps and the draft contains the requested set.
Requirement: Deliver every commissioned item in one rich bubble rather than reducing the set to selected items or themes.
Not applicable. The draft did not contain the requested set of 10 events.
include_recommendation_links
Not applicableAdvisoryApplies when: Hark delivers a table of options or recommendations and the draft supplies destination links.
Requirement: Include each destination in its own link column so the user can open every recommendation.
Not applicable. No table of options or recommendations was delivered.
keep_deliverable_companions_brief
Not applicableAdvisoryApplies when: Hark places prose before or after a commissioned-work rich bubble.
Requirement: Use at most one framing sentence before and one takeaway sentence after the card, each at or below 20 words.
Not applicable. The response contains no commissioned-work rich bubble.
isolate_single_links
Not applicableAdvisoryApplies when: Hark shares exactly one URL that is worth opening.
Requirement: Put the link alone in a link bubble, written as its placeholder when the draft gave one and otherwise as the exact URL. Do not place it inside a prose bubble, and do not send a bubble that only labels the link.
Not applicable. The response shares three URLs, not exactly one.
avoid_request_restatement
Not applicableAdvisoryApplies when: Hark repeats part or all of the user's request.
Requirement: Restate the request only when doing so resolves an ambiguity or is necessary for confirmation.
Not applicable. The response does not restate the user’s request.
make_progress_updates_material
Not applicableAdvisoryApplies when: The draft contains a progress update and the input does not say the task is still running.
Requirement: Send only a new fact, completed result, observed blocker, or changed estimate that the draft offers.
Not applicable. The draft and delivered response do not provide a task-progress update.
compress_summary
Not applicableAdvisoryApplies when: Hark provides a summary.
Requirement: Put the summary in one document bubble and keep it materially shorter than the source.
Not applicable. The response is not a summary.
follow_summary_instructions
Not applicableAdvisoryApplies when: The user requests a summary with a specified length, format, audience, focus, or reading level.
Requirement: Follow the requested summary constraints when the draft carries them and they remain compatible with the required document-bubble delivery.
Not applicable. The user did not request a summary.
use_default_summary_length
Not applicableAdvisoryApplies when: The user requests a summary without specifying a length or format.
Requirement: Use one document bubble whose content is normally no more than a couple hundred words, extending only when the source's section count requires it.
Not applicable. The user did not request a summary.
preserve_summary_skeleton
Not applicableAdvisoryApplies when: Hark provides a summary.
Requirement: Keep the source's own skeleton while making each section or act a short numbered line.
Not applicable. No source summary was provided.
preserve_summary_order
Not applicableAdvisoryApplies when: Hark summarizes a source with sections or acts.
Requirement: Preserve the source's section or act order and do not drop one.
Not applicable. No sectioned or act-based source was summarized.
keep_summary_qualifications_local
Not applicableAdvisoryApplies when: A summarized statement needs a qualification.
Requirement: Keep the qualification next to the summarized statement it modifies.
Not applicable. The response is not a summary.
use_summary_numbered_lines
Not applicableAdvisoryApplies when: Hark formats a structured-source summary.
Requirement: Use short numbered lines inside the document bubble instead of flat prose bubbles.
Not applicable. The response is not a structured-source summary.
present_partial_result_before_blocker_detail
Not applicableAdvisoryApplies when: Hark has a useful partial result and also reports a blocker.
Requirement: Present the partial result first and keep any blocker explanation compact.
Not applicable. No useful partial event result was available; the response only had blocker and source-status information.
omit_running_task_updates
Not applicableAdvisoryApplies when: The input says a task is still running.
Requirement: Send no response about the running task. Do not claim a lack of access, suggest the user do it, or announce that work continues.
Not applicable. The task was not still running when the final response was sent.
preserve_code_exactly
Not applicableAdvisoryApplies when: The draft contains a code block the user needs.
Requirement: Copy the code byte for byte into one code bubble with its language and a short sentence-case title.
Not applicable. No needed code block appears in the draft.
preserve_document_exactly
Not applicableAdvisoryApplies when: The draft contains an email, message, template, letter, exact quote, or list meant for use elsewhere.
Requirement: Copy the full text byte for byte into one document bubble. A message the user is meant to send, paste, or forward is always a document bubble, never prose. A composed summary card is the only exception.
Not applicable. The draft contains no email, message, template, letter, exact quote, or reusable list requiring document delivery.
preserve_attachment_names
Not applicableAdvisoryApplies when: The input lists an attachment riding with the reply.
Requirement: Put each attachment in its own matching attachment bubble and use the attachment's exact input name.
Not applicable. No attachment rides with the reply.
provide_rich_metadata
Not applicableAdvisoryApplies when: Hark sends a table, code, or document bubble.
Requirement: Give tables pipe rows, a short title, and the Excel Spreadsheet subtitle. Give code its language and title. Give documents a title and the .txt file subtitle.
Not applicable. No table, code, or document bubble was sent.