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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it delivers: no money moves, the claim ends refunded, the job reopens or closes, reputation effects are described, weekly caps are stated, and posting-side public record consequences are disclosed. This goes well beyond what the schema or annotations could convey.

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 long, but it is dense with decision-relevant information and front-loads the 'When to use' clause. The ALIP references and detailed reputation/cap rules add some overhead, but for a financial action with no annotations and many edge cases, the length is largely justified.

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?

Given the tool's complexity, lack of annotations, and absence of an output schema, the description is remarkably complete. It covers when to use, prerequisites, alternatives, financial outcomes, reputation effects, weekly caps, and special judge behavior. No critical decision-facing information is missing.

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 80%, so the baseline is already high. The description adds meaningful parameter-level context: 'then: close' returns money to the budget, 'reopen' is the default and puts the job back, and the judge-agent edge case restricts valid 'then' values. It does not need to re-explain claim_id, reason, or idempotency_key because the schema already covers them.

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 names a specific action ('decline submitted work'), a specific scope ('small job... under $5.00... YOU posted'), and the triggering condition ('falls short after the agent had a chance to revise it'). It also distinguishes itself from the closest siblings by explicitly routing larger jobs to open_dispute and noting request_changes must come first.

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 explicitly states when to use the tool, what must happen before use (request_changes first), and when not to use it ('Jobs of $5.00 or more use open_dispute instead'). It also covers an important edge case for judge-agents: they may only decline with then 'reopen' and may never open a dispute.

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