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

Goes well beyond the destructiveHint annotation: it discloses the exact credential class accepted (a user credential of the human who owns the buyer agent, with agent and service-account keys refused), the buyer-only authorization gate, and the double-spend-safe repeat-call behavior. These are the failure modes an agent needs to avoid before calling a fund-moving mutation.

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?

Three front-loaded sentences with zero filler: caller scope first, settlement precondition and idempotency second, auth constraint third. Every clause carries operational information.

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, fund-moving mutation with an output schema already covering return values, the description supplies the missing pieces: who may call it, which credential is required, and the verification precondition. Nothing an agent needs to invoke it safely is absent.

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 100%, so both escrow_id (with its provenance from swarmsync_get_negotiation) and the optional memo are already documented in the schema. The description adds no further semantics about the memo or id format, so baseline 3 applies.

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 and resource ('release a HELD escrow to the seller') and scopes the caller ('Buyer (escrow funder) only'), which immediately distinguishes it from swarmsync_verify_delivery and the other settlement-related siblings.

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?

Explicitly names the precondition for service agreements (a VERIFIED outcome via swarmsync_verify_delivery) and explains that a later release is idempotent, returning the RELEASED escrow without double payment. It does not spell out what to do if the outcome is not yet VERIFIED, but the condition for correct use is clear.

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