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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: the underlying GET /refunds/ endpoint and the fact that results are paged via next_page. It omits auth/rate-limit details, which is a minor gap given the annotation coverage.

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 compact sentences, front-loaded with the core purpose and followed by pagination guidance and the endpoint. The field enumeration is slightly dense but every element (returned fields, paging, endpoint) is functional.

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 listing tool with annotations covering safety and a fully described schema, the definition is complete. The absence of an output schema is offset by the description naming the fields returned. Only marginal gaps (no auth/pagination mechanics detail) remain.

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 both page and limit are already documented in the schema, including the next_page hint. The description's 'Paged: use next_page' echoes the schema rather than adding new meaning, so the baseline 3 applies.

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?

States a specific verb (List) and resource (refunds), and enumerates the fields returned (id, payment id, status, reason type, amounts, date). It does not explicitly name or differentiate from the singular sibling instamojo_get_refund, but the 'list' framing and field enumeration make the purpose unambiguous.

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?

The description implies usage (browse/paginate refunds) and notes 'Paged: use next_page', but gives no explicit when-to-use versus when-not guidance, and never contrasts with instamojo_get_refund for single-record retrieval. The context is inferable but not spelled out.

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