ebay_get_cancellation_requests

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

The description explicitly states the tool is read-only, uses the Fulfillment API (not deprecated Post-Order API), and returns orders matching cancellation criteria. This is good transparency for a read-only tool, though it lacks details on pagination or error handling.

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 concise and front-loaded with the main purpose, followed by technical details and OAuth scope. It could be slightly more streamlined, but it avoids unnecessary fluff.

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?

Without an output schema, the description partially explains what is returned (orders filtered by cancelState) but does not describe the response structure or mention that only up to maxResults orders are scanned. This leaves some ambiguity for the agent.

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 input schema already fully describes both parameters (filter and maxResults) with 100% coverage. The description adds no additional semantic information beyond the schema, so a baseline score of 3 is appropriate.

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 scans for cancellation requests from seller orders by calling the Fulfillment API getOrders and filtering by cancelState. It distinguishes itself from generic order retrieval tools like ebay_get_orders by focusing specifically on cancellations.

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 indicates the tool is a read-only helper and specifies required OAuth scopes, giving context for safe usage. It does not explicitly contrast with alternatives or provide when-not-to-use guidance, but the purpose is clear enough for an agent to infer appropriate use cases.

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