Get Refund Order Details

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

Annotations already indicate read-only and non-destructive nature. The description adds the 60-day limit and the requirement of merchant_id, and explicitly warns against using data fields or error messages as triggers, providing context beyond annotations.

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?

The description is a single, well-structured paragraph that begins with identifying tags, then purpose, constraints, and warnings. It is efficient but slightly dense; each sentence adds value.

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?

Given the presence of an output schema for return values, the description adequately covers purpose, required parameters, constraints, and usage warnings. It lacks detail for optional parameters but is otherwise complete for a read-only retrieval tool.

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?

With 0% schema description coverage, the description only covers the required parameters (merchant_id, start_date, end_date) at a high level, but does not explain the optional 'page' and 'per_page' parameters or the expected date format, leaving significant gaps.

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 clearly states the verb 'fetch', the resource 'refund order details', and the scope 'within a date range'. It distinguishes itself from siblings like 'create_refund' by focusing on retrieval rather than creation.

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?

Explicitly states required parameters (merchant_id, start_date, end_date), a constraint (maximum 60-day range), and a clear directive to only call when explicitly requested by the user, avoiding unintended invocations.

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