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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds only a list of return categories (records, checks, next steps, guides), which is thin given the output schema already exists; no auth, rate-limit, or scoping context is provided.

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?

A single compact sentence with no filler. It is efficient, though the action verb is buried behind the 'choose the parameters' framing rather than front-loaded.

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?

An output schema exists so return values need not be explained. However, with 0% schema description coverage and no sibling differentiation, the description leaves key gaps about enum semantics and tool selection that a complete definition would close.

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 0%, so the description carries the full burden for the two enum parameters. It names them generically as 'stage' and 'preparation topic' but never explains what values like 'statement3', 'annexureb', 'notice', or 'filed' mean or how they combine, leaving the enum meaning to inference.

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: retrieve records, checks, next steps and guides for a service-export refund checklist. It conveys the domain well, though it does not explicitly distinguish itself from read_refund_guide or search_refund_guides.

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?

Usage is only implied – the description tells the agent to 'choose the stage and topic' but gives no when-to-use guidance or comparison against sibling tools like read_refund_guide or search_refund_guides.

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