search_cancellations_tool

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

No annotations are provided, so the description carries the full disclosure burden. It hints at return content (refunds, cancel reasons) but says nothing about pagination behavior despite page_size/next_page_token parameters, nor about permissions 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 tight sentences with the core purpose front-loaded and the date-format hint appended. No filler, though the second sentence is doing parameter work rather than usage work.

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, but with 8 undocumented parameters and no annotations, the definition leaves too many invocation details (filtering by seller, timezone semantics, pagination) to guesswork.

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% across 8 parameters, and the description only clarifies the format of start_date/end_date. seller_name, timezone, page_size, next_page_token, and create_time_ge/lt are left entirely undocumented.

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+resource ('Search cancelled orders') and adds the distinguishing payload ('refund amounts and cancel reasons'), which separates it from sibling search_returns_tool and the order-list tools. It does not explicitly name an alternative, so it stops short of 5.

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 only guidance is a parameter-format hint ('Use start_date/end_date (YYYY-MM-DD) or raw timestamps'). There is no statement of when to choose this tool over search_returns_tool or get_shop_orders_tool, and no exclusions or prerequisites.

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