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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is known without the description. The description adds nothing beyond that: it doesn't say what state the escrow enters, whether the action is reversible, what permissions are needed, or why the operation is flagged destructive. Given a destructive, idempotent mutation, at least one of those facts should be spelled out.

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 single short phrase is front-loaded and free of filler, so nothing is wasted. But the brevity is under-specification rather than elegance — there is no structure, no second sentence carrying usage or behavioral detail.

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 destructive, state-changing DeFi operation with a nested unknown-shape parameter, no output schema, and zero schema documentation, the description supplies no information an agent would need to call it correctly. Nearly everything must be inferred from the tool name alone.

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 0% and the description explains none of the three parameters. In particular, 'evidence' is a nested object with no documented shape or content expectations, and 'reason' has no stated format or length constraints. The description does nothing to compensate 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?

The phrase 'Open escrow dispute' names a verb and resource, so the agent can infer it initiates a dispute on an existing escrow. However, it does not distinguish this from siblings like escrow_create, escrow_release, or verify_settlement, and the bracket tag '[defi]' adds no disambiguation. Purpose is inferable but not sharply defined.

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?

There is no statement of when to open a dispute versus releasing escrow or creating one, no prerequisites (e.g., must the escrow exist or be funded?), and no mention of alternatives among the escrow_* siblings. The agent must guess the trigger conditions entirely.

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