ebay_get_cancellation_requests

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

Annotations declare readOnlyHint=true, and the description reinforces this with 'Read-only helper.' It adds meaningful behavior beyond the annotation: it calls the Fulfillment API getOrders, filters on cancelState, avoids the deprecated Post-Order API, and specifies the required OAuth scope. No contradiction with 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 compact and front-loaded: the purpose appears in the first sentence, implementation detail follows, and the OAuth scope is appended cleanly. Every sentence earns its place with no filler or repetition of the tool name.

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?

Despite no output schema, the description explains what is returned (orders with cancelState not NONE_REQUESTED or cancel requests), necessary auth scope, and underlying API behavior. It is complete enough for an agent to invoke correctly, though pagination/date-range defaults are not explicitly spelled out.

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 coverage is 100%, so the schema already documents filter and maxResults well. The description adds little parameter-specific detail beyond saying 'recent seller orders' and 'via getOrders,' which is enough for a baseline 3 since the schema carries the parameter semantics.

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 states a specific verb ('Scan') and resource ('seller orders for cancellation requests'), and explicitly says it calls Fulfillment API getOrders and filters by cancelState. This clearly distinguishes it from the sibling ebay_get_orders, which returns all orders.

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 intended use case is clear: scan recent seller orders for cancellation requests. It also states it is a read-only helper and does not use the deprecated Post-Order API, giving useful routing context. However, it does not explicitly name ebay_get_orders as the alternative when unfiltered orders are needed.

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