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

Beyond the annotations (destructiveHint, idempotentHint, openWorldHint), the description discloses that the call atomically freezes release and refund, that 0.10 USDC is charged via x402 on Base mainnet under a 10-call/30-day free tier, that X-Wever-Wallet-Proof must be bound to the exact arguments and path, and that disputes expire after 14 days with a signed refund receipt subject to a UTC daily cap. That is unusually rich destructive/authorization/pricing disclosure.

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 action and target are front-loaded in the first clause, and the dense remainder is mostly load-bearing (rejection rules, fee model, auth header, expiry). Some fragments ('No new principal enters.') border on cryptic, but there is little pure padding.

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 complex, paid, authorization-gated mutation with a nested-object schema, no output schema and no annotations covering pricing, the description covers preconditions, cost, auth binding, expiry and recovery routing. The main gap is that the shape of the returned receipt/state is never described, which matters since no output schema exists.

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 0% schema description coverage, the description partially compensates: 'claim reference' maps to the nested claim object, and 'escrow ... or ... work order' implies the oneOf choice between escrow_id and order_id. It says nothing about idempotency_key semantics or the reason_code enum, leaving roughly half the parameters undocumented in both schema and prose.

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 states a specific verb and resource – 'Either escrow party opens a dispute against already funded escrow or a funded work order' – and scopes the precondition (already funded). It is a clear, agent-legible action, though it never names or routes against dispute-adjacent siblings such as wever_dispute-submit-evidence or wever_workorder-dispute, so it stops short of full sibling differentiation.

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 concrete when-not conditions ('Rejects locked value above 25.00 USDC, unfunded or already disposed funds, and unrelated wallets') and points to /api/dispute-contract for authorization and recovery limits. It does not, however, tell the agent which sibling to use instead for evidence submission or resolution, so it is clear context without explicit alternatives.

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