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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is known without the description. The description adds essentially nothing beyond that: it does not say whether a decline is final or reversible, whether the offer is released or cancelled, or that the terms hash is validated before committing. For a destructive action that gap is material.

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?

A single front-loaded sentence with no filler. It is efficient, but its brevity is partly under-specification rather than disciplined compression.

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?

A destructive, idempotent tool with three required parameters, no output schema, and an implied two-step workflow with inspect_offer. The description does not explain the terms-hash handshake, the reason field, or what the caller gets back, leaving an agent to guess at a consequential operation.

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 only 25%; only 'token' is documented. The required 'terms_sha256' is an opaque hash whose provenance (presumably an inspect_offer result) and mismatch behavior are unexplained, and 'reason' (maxLength 500) is never mentioned. With low coverage the description needed to compensate and does not.

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 plus resource ('Decline an issued offer') and is readily separable from the sibling accept_offer. The 'on its inspected terms' qualifier signals a prerequisite relationship with inspect_offer, though it is phrased obscurely.

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 phrase 'on its inspected terms' implies the offer must be inspected before declining, and that this is the counterpart to accept_offer. It never says when a decline is appropriate, what alternatives exist, or what happens if the offer was not inspected.

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