ebay_get_payment_dispute_summaries

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

No annotations are provided. The description indicates a read operation ('Get summaries') and specifies required OAuth scope, but does not disclose any behavioral traits such as rate limits, data freshness, or whether it returns only open/closed disputes by default.

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 two sentences plus OAuth scope, front-loaded with the purpose. Every sentence serves a purpose, with no wasted words.

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?

No output schema is present, and the description does not explain what a 'summary' contains or mention pagination behavior (limit/offset). Given the lack of annotations and moderate complexity, more detail on return structure or pagination defaults is needed.

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 100%, so baseline is 3. The description adds general filter guidance but does not provide additional meaning beyond what the param descriptions already contain, such as examples or relationship between filters.

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 'Get summaries of all payment disputes', using a specific verb and resource. It implies a list operation, distinguishing it from sibling tools like ebay_get_payment_dispute (single dispute) and ebay_get_payment_dispute_activities (activities for a dispute). However, it does not explicitly differentiate from these siblings.

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 mentions using filters to narrow results, but lists only 'dispute status, buyer username, or order ID', which partially matches the schema parameters (openFilter, buyerFilter, orderFilter). No guidance on when to use this tool versus alternatives, or prerequisites beyond OAuth scope.

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