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

With no annotations, the description carries the full behavioral burden and discloses meaningful side effects: workspace owners/admins are emailed and subscribed endpoints receive dispute.opened. It also states authentication/workspace prerequisites and the sandbox 403 failure mode. It stops short of covering idempotency, duplicate handling, or the caller's required role.

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 three sentences, front-loaded with the purpose and the required parameters. Side effects and auth prerequisites follow in a logical order with no filler. The final sentence is dense but each clause earns its place.

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 moderately complex creation tool with no annotations, it covers purpose, required/optional parameters, defaults, side effects, and auth prerequisites well enough to call correctly. Since there is no output schema, the absence of return-shape or idempotency details is a minor remaining gap.

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 the baseline is 3. The description adds useful grouping of required versus optional parameters and adds the status default of 'open', which is not stated in the schema. It repeats the schema's currency default and otherwise does not add deep semantics 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 immediately states a specific creation verb and resource: 'Open a payment dispute.' The 'open' framing distinguishes creation from the sibling update_dispute tool, even though no sibling is named explicitly. It also lists the core required fields, making the operation concrete.

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?

It gives clear invocation context: payment_id and amount are required, several fields are optional, and the caller needs a claimed Last Price credential and claimed workspace. It also states a when-not condition: an unclaimed sandbox key is refused with 403. However, it does not explicitly say when to use this instead of update_dispute or get_dispute.

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