Get cancellations

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

The description is consistent with the readOnlyHint annotation, indicating a safe read operation. It adds the behavioral trait that cancellations are buyer-initiated. However, it does not disclose pagination behavior, data returned, or any side effects. With annotations already marking it read-only, the description adds some but not significant value.

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 clear sentence with no wasted words. However, it could be expanded to cover key aspects like pagination or filtering without becoming verbose. It is appropriately front-loaded but too brief to cover all necessary information.

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 4 parameters (pagination, status, platform) and no output schema, the description is far from complete. It does not mention pagination with cursor/limit, possible status values, platform filtering, or what the response contains. The tool is simple but the description leaves significant gaps.

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?

The description does not explain any parameters. Schema coverage is 75% (3 of 4 parameters documented), but the description contributes no additional meaning. The 'status' parameter lacks a description in both schema and description. The description should clarify filtering options, default values, or format requirements.

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 tool lists buyer-initiated cancellation requests, using a specific verb (List) and resource (cancellation requests). The qualifier 'buyer-initiated' distinguishes it from seller-initiated cancellations and from sibling tools like respond_to_cancellation which handles responses.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools include respond_to_cancellation (for actions on cancellations) and get_orders (for order details). The description does not mention any prerequisites, exclusions, or context for the tool.

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