Show what a question set expands to

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description's 'Echo' wording is consistent with those annotations, but it adds no extra behavioral detail such as error behavior, auth needs, or rate limits.

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?

Two short sentences with zero waste: the first states the purpose, the second states when to use it. Information is front-loaded and appropriately sized.

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 simple read-only expansion tool with rich annotations, full schema description coverage, and an output schema, the description covers purpose and usage sufficiently. It could be slightly more complete by clarifying how preset and inline questions relate or which one takes precedence.

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 description coverage is 100%, so the schema already documents both parameters ('Preset name' and 'Inline questions'). The description mentions output fields, not input semantics, and adds no clarification about how preset and questions interact; baseline 3 is appropriate.

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 ('Echo') and resource ('a question set'), and enumerates the expanded fields (ids, kinds, options, levels). It is clear what the tool does, though it does not explicitly distinguish itself from siblings like list_presets or decide.

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 a clear usage context: 'Call this when you need the exact option labels before deciding.' This implicitly positions it ahead of decision-making siblings, but it does not name an alternative tool or state when not to use it.

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