list_refunds

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

No annotations are provided, so the description carries the full burden. It states the basic listing function and the optional booking filter, but does not disclose behavior like pagination via max_items, default limits, ordering, or whether refunds are read-only (seemingly implied by 'list' but not explicit).

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 clear sentence with no filler. It front-loads the core action and the one meaningful variant (single booking), making it easy to scan.

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?

The tool is simple with only two optional parameters and an output schema exists, so the description doesn't need to cover return values. However, it lacks guidance on max_items usage and does not position the tool relative to payments/fees, leaving some gaps for an agent trying to decide between list tools.

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%. The description only hints at booking_id ('optionally for a single booking'), leaving max_items completely undocumented. The schema provides defaults and types, but the description does not explain how max_items behaves or what the parameters actually mean in the refund context.

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 uses a specific verb ('List') and a specific resource ('guest refunds'), and adds an optional filter ('for a single booking'). This clearly distinguishes it from sibling tools like list_payments or list_bookings.

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?

There is no guidance on when to use this tool versus alternatives such as list_payments or list_fees, and no mention of when filtering by booking_id is appropriate or required. The only hint is the optional booking filter, but no explicit comparison or exclusion.

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