purchases_voided_list

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

No annotations provided, so description should disclose behavioral traits. It only says 'List' (read operation) but doesn't mention authorization needs, pagination, rate limits, or side effects. Significant gap for a tool with 8 parameters.

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 sentences, front-loaded with purpose and filtering capability. Efficient, though could be more structured to list specific filter parameters.

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?

With 8 undocumented parameters, no output schema, and no annotations, the description is too sparse. It only addresses two filtering aspects, leaving out pagination (maxResults, startIndex, token) and other options (includeQuantityBasedPartialRefunds).

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 only 13% (only packageName described). The description hints at 'time range' (likely startTime/endTime) and 'voided source' (likely type), but does not explain any other parameters or their roles. Fails to compensate for low coverage.

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?

Clearly states it lists voided purchases (refunded/charged-back), using specific verb and resource. Distinguishes from sibling purchase tools that deal with non-voided purchases.

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?

Mentions filtering by time range and voided source, giving basic usage context. However, lacks explicit guidance on when to use this tool vs. alternatives like order refund or subscription cancellation tools among siblings.

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