Respond to dispute

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

The description adds value beyond the destructiveHint annotation by explicitly stating that the action 'changes live shop data' and 'requires the seller's explicit confirmation before it executes'. This gives the agent clear behavioral insight into the tool's impact and prerequisites.

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 short sentences plus a critical warning, which is efficient and front-loaded. Every sentence conveys essential information without redundancy.

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 the destructive nature and multiple parameters, the description does not explain the return value, the dispute lifecycle, or what 'sellers explicit confirmation' entails. It lacks details on the confirmation_token parameter, leaving the agent uncertain how to handle asynchronous approval. The description is incomplete for full autonomous use.

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?

With only 33% schema description coverage, the description should help clarify parameters, but it contributes nothing about any of the 6 parameters, including required fields like dispute_id and message. The agent must rely solely on the schema, which is insufficient for a complex tool.

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 'submit the seller's response/evidence to a dispute or complaint', which is a specific verb and resource. However, it does not differentiate from sibling tools like respond_to_cancellation or respond_to_return, so it misses the top score.

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 does not provide guidelines on when to use this tool versus alternatives. It mentions that it requires seller's explicit approval, but that is a constraint, not usage context. No mention of when not to use it or references to sibling tools.

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