ebay_accept_payment_dispute

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

With no annotations, the description carries full burden. It discloses the action results in a refund but lacks detail on side effects (e.g., irreversibility, impact on seller metrics). The mention of OAuth scope adds some transparency.

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 very concise with two sentences plus scope info. Every sentence serves a purpose, and the main action is front-loaded.

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?

For a straightforward tool, the description covers purpose, usage condition, and parameter nuance. However, it lacks explanation of return values or potential consequences like dispute closure. Given no output schema, slightly more context could help.

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 baseline is 3. The description adds value by noting that returnAddress is required for ITEM_NOT_RECEIVED disputes, which provides conditional context beyond the schema.

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 action ('Accept a payment dispute'), the resource ('payment dispute'), and the condition ('when you agree with the buyer claim'). It effectively distinguishes from sibling tools like ebay_contest_payment_dispute.

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 explicitly says 'Use this when you agree with the buyer claim,' providing clear context. It also mentions the required OAuth scope. However, it does not explicitly name the alternative tool for disagreeing, though sibling context implies it.

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