← Back to scenario detail
Response style analysis
Applied 45 · Passed 34 · Failed 11 · Not applicable 23
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
The travel events page is down, so I pulled these from JNTO's Japan in October guide and the linked festival pages. Admission prices aren't listed by JNTO almost everywhere, and no deadline showed up on any of them.
### October 2026 Events · Japan Travel
| Event | Dates | City | Venue | Admission | Booking deadline |
|---|---|---|---|---|---|
| [Nagasaki Kunchi](https://www.japan.travel/en/spot/343/) | Oct 7–9 | Nagasaki | Suwa Shrine, 18-15 Kaminishiyama-machi | not stated; street events and food stalls open | none stated |
| [Takayama Autumn Festival](https://www.japan.travel/en/spot/150/) | Oct 9–10 | Takayama, Gifu | Sakurayama Hachimangu Shrine, 178 Sakura-machi | free to watch; small fee for English audio guide | none stated |
| [Otsu Festival](https://www.japan.travel/en/spot/1061/) | weekend before Sports Day (2nd Mon of Oct) | Otsu, Shiga | Tenson-jinja shrine area | not stated | none stated |
| [Mino Washi Akari Exhibition](https://www.japan.travel/en/spot/155/) | weekend before Sports Day | Mino, Gifu | old town streets, ~400 lamp artworks | not stated | none stated |
| [Ikegami Honmonji Oeshiki](https://www.japan.travel/en/spot/1650/) | Oct 11–13, lantern parade Oct 12 | Tokyo (Ota-ku) | Ikegami Honmonji Temple, 1-1-1 Ikegami | not stated | none stated |
| [Nada Fighting Festival](https://www.japan.travel/en/spot/26/) | Oct 14–15 | Himeji, Hyogo | Matsubara Hachiman Shrine, 399 Shirahamacho | not stated | none stated |
| [Nikko Toshogu Shuki Taisai](https://www.japan.travel/en/spot/297/) | mid-October | Nikko, Tochigi | Toshogu Shrine, 2301 Sannai | not stated | none stated |
| [Kawagoe Festival](https://www.japan.travel/en/spot/325/) | third weekend of October | Kawagoe, Saitama | Kurazukuri district, Hikawa Shrine, 2-11-3 Miyashita-machi | not stated | none stated |
| [Kurama Fire Festival](https://www.japan.travel/en/spot/67/) | Oct 22 | Kyoto (Kurama) | Yuki-jinja Shrine and village streets | not stated; arrive early for a viewing spot | none stated |
| [Jidai Matsuri](https://www.japan.travel/en/spot/88/) | Oct 22 | Kyoto | Imperial Palace to Heian-jingu, 4.6 km route | free along the route; priority seating tickets sold in advance at convenience stores | in advance, no date given |
Tokyo International Film Festival runs roughly 10 days in late October, is ticketed, and spans Hibiya, Ginza, and Yurakucho.
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 changes the precise HTTP 404 result into the broader claim that the page “is down,” which changes the scope and certainty of the factual statement.
lead_with_outcome
FailAdvisoryApplies when: Hark sends a user-visible response.
Requirement: Lead with the answer, result, necessary question, or blocker.
The response begins with the unavailable source page and sourcing explanation instead of the requested event results.
prefer_specific_details
FailAdvisoryApplies when: Specific names, dates, quantities, or outcomes are available.
Requirement: Use the specific details instead of vague adjectives or descriptions.
The response says the page “is down” rather than giving the available, specific HTTP 404 status.
keep_one_thought_per_bubble
FailAdvisoryApplies 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.
The first prose bubble combines two distinct thoughts: the source-page limitation and the absence of admission prices and deadlines.
include_recommendation_links
FailAdvisoryApplies 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.
Each event has a destination link, but the links are embedded in the Event column rather than placed in their own link column.
keep_deliverable_companions_brief
FailAdvisoryApplies 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.
The prose before the table is about 38 words, exceeding the 20-word limit for a framing sentence.
answer_before_background
FailAdvisoryApplies when: Hark provides an answer or outcome with supporting background.
Requirement: Give the answer or outcome before the background detail.
The sourcing background and limitation appear before the event results.
avoid_routine_tool_narration
FailAdvisoryApplies when: Hark describes its research or routine tool use.
Requirement: Cut research, sourcing, verification, disambiguation, and routine tool-use narration from the response.
The opening narrates the sourcing process by saying, “I pulled these from” the guide and linked pages.
present_partial_result_before_blocker_detail
FailAdvisoryApplies when: Hark has a useful partial result and also reports a blocker.
Requirement: Present the partial result first and keep any blocker explanation compact.
The source blocker and missing-field explanation are presented before the useful event table.
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.
The first companion exceeds the allowed length, and the final companion adds an eleventh event rather than serving only as context, a caveat, or a concise takeaway for the card.
provide_rich_metadata
FailAdvisoryApplies 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.
The table has pipe rows and a short title, but no observable “Excel Spreadsheet” subtitle is provided.
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 response gives exactly 10 events in a comparison table with dates, city, venue, admission, and booking deadline fields.
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 delivered response retains the draft’s selected 10 events, source caveat, missing-information caveat, and additional Tokyo International Film Festival note.
preserve_instruction_direction
PassAdvisoryApplies 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.
User-directed details such as arriving early and buying priority seating tickets in advance retain their actions and objects.
avoid_invented_content
PassAdvisoryApplies 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.
The delivered claims and options all appeared in the draft supplied to the delivery layer.
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 direct wording, and each prose bubble is concise.
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 source and availability explanation is brief and does not belabor basic points.
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 starts with a material source limitation rather than praise, generic acknowledgment, or an offer.
use_structure_only_when_helpful
PassAdvisoryApplies 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 comparable event information is presented as a table rather than reconstructed as prose.
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 response generally uses plain language and clear field labels.
use_hark_first_person
PassAdvisoryApplies 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.
The response refers to its work using first person and does not mention editing rules, prompts, or a draft.
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.
The response uses the direct imperative “arrive early” where appropriate.
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 reply uses two prose bubbles around one rich table, staying within the allowed limit.
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.
Both prose bubbles are under 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 bubbles use capitalization and end every sentence with a period.
avoid_prose_markup
PassAdvisoryApplies 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 plain-prose bubbles contain no lists, headers, Markdown, emoji, em dashes, or punctuation hyphens.
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 event row or prose statement is duplicated elsewhere in the reply.
choose_collection_format_for_comparison
PassAdvisoryApplies 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.
The 10 events share a common schema and are delivered in one comparison table.
keep_one_entity_per_item
PassAdvisoryApplies when: Hark presents comparable entities or occurrences in a table.
Requirement: Put one comparable entity or occurrence in each row.
Each table row contains one event.
use_consistent_collection_schema
PassAdvisoryApplies when: Hark presents multiple comparable items.
Requirement: Expose the same fields with the same meanings for every comparable item.
Every event uses the same six fields with consistent meanings.
keep_comparable_detail
PassAdvisoryApplies 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.
The table preserves the draft-provided details for each of the 10 selected events, including qualifications and availability notes.
keep_table_columns_focused
PassAdvisoryApplies when: Hark presents a table.
Requirement: Keep columns focused on the user's decision or question.
The columns directly reflect the event identity and the five details requested by the user.
keep_every_commissioned_item
PassAdvisoryApplies 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.
All 10 commissioned events are included together in one table.
preserve_link_urls
PassAdvisoryApplies 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 event URLs retained from the draft are presented without shortening or domain-only substitutions.
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.
Because the user commissioned a set of 10 events, the response appropriately retains all 10 and the requested fields.
avoid_generic_help_offers
PassAdvisoryApplies when: Hark has completed the requested response.
Requirement: Do not append a generic offer of further help.
The delivered response does not append a generic offer of further 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.
The response states that the requested page is unavailable and explains that admission prices and booking deadlines were not available from the replacement JNTO pages.
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.
The response does not expose stack traces, internal tool names, provider payloads, or implementation details.
avoid_repeated_apology
PassAdvisoryApplies when: Hark reports a blocker or failure.
Requirement: Avoid repeated apologies and generic failure language.
The response reports the limitation without any repeated apology or 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 two plain-prose bubbles contain no Markdown; the structured content is isolated in the table message.
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.
Although the table has six columns, each is necessary to carry the event identity and all five requested comparison fields.
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 full event result is included directly in the response rather than only referenced by 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.
The table is isolated in its own message, separate from the prose bubbles.
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 observable delivery separates two prose messages from the structured table message, matching their content types.
limit_rich_bubbles
PassAdvisoryApplies when: Hark sends rich content.
Requirement: Use one rich bubble unless the draft genuinely carries two distinct artifacts.
The response uses one rich table bubble.
Not applicable
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, not a serious, painful, or high-stakes matter.
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.
avoid_delivery_pointers
Not applicableAdvisoryApplies 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.
Not applicable. The response does not direct the user above, below, or to a saved location for the answer.
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.
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 more than one URL.
group_related_links
Not applicableAdvisoryApplies 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.
Not applicable. The URLs are destinations attached to comparable table items, so the table-specific recommendation-link rule governs their presentation.
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 in prose.
avoid_repeated_conclusions
Not applicableAdvisoryApplies 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.
Not applicable. The response does not repeat the same conclusion in multiple places.
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 delivered response is a final result, not a 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 requested 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. The response is not a summary of a structured source.
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. The response is not a section-by-section or act-by-act summary.
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.
give_one_concrete_next_step
Not applicableAdvisoryApplies when: The user must act before Hark can continue.
Requirement: State one concrete next step only when the draft offers it.
Not applicable. The user does not need to act before Hark can continue.
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 input indicates that no task remained running when the response was delivered.
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 user-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 document that required byte-exact 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.