Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is carried structurally. The description usefully adds that 'skip'/'enough' close the question, but says nothing about irreversibility, who consumes the answer, or what happens to text beyond the character cap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and target, with no filler. The telegraphic phrasing ('decision skip or enough closes it') is slightly cryptic but compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world mutation with no output schema, the description covers the essential call and close semantics but omits consequences of closing (is the question gone permanently?) and how the 'ask the human' path interacts with the quest flow. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, including descriptions for id, text length limits, the decision enum, and the idempotency key, so the schema does the heavy lifting. The description only restates the id source and the effect of the decision values, adding little beyond structured data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Answer a quest's Bar question') and identifies the target item type ('needs_human bar_question id'). It is clearly distinct from siblings like interview_answer or chat_summary, though it never names an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete operational guidance: answer from known facts, ask the human for unknowns, and use 'skip'/'enough' to close without an answer. It lacks explicit when-not conditions or named alternative tools, but the selection among text vs. decision is spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.