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

Goes well beyond the annotations by disclosing that the dispute is never published, that it marks the task disputed, that it does not freeze escrow or issue a refund automatically, and that the provider has 72 hours to answer at reply_to. These are exactly the side-effect and scope details an agent needs before triggering a non-destructive but open-world write, and they are consistent with destructiveHint=false.

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?

Three tight sentences, front-loaded with the identity of the operation, then the side effects, then the counterparty timeline. No filler and every clause carries information an agent would otherwise have to guess.

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 non-idempotent state-changing tool with no output schema, the description covers scope, side effects, and the follow-up window well. It leaves open what happens after 72 hours and what the call returns, but those gaps are modest relative to what is already disclosed.

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 50%, and the description adds real meaning only for reply_to by explaining that the provider's 72-hour answer goes there. The required 'reason' and optional 'sender' parameters are documented nowhere, and 'id' is only echoed ('task or invoice'), so the description only partially compensates for the coverage gap.

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?

States a specific verb and resource: 'Notifies the provider of a private dispute about a task or invoice.' The qualifier 'private ... never published' sharply separates it from public reporting/action tools among the siblings (report_payment, request_action), and citing 'terms, section 12' anchors it to a concrete policy scope.

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 gives clear context for what triggers this tool (a dispute over a task or invoice) but offers no explicit when-to-use vs. when-not guidance against siblings like report_payment or request_action, nor any prerequisites such as whether the task must be in a specific state. Usage is inferable but not spelled out.

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