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

Annotations already declare the mutation/safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower; the description nonetheless adds substantive behavior: budget held in escrow, release gated on verification passing, and a RECEIPT that is third-party verifiable and portable. This explains the money and trust semantics an agent cannot infer from annotations alone.

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?

Front-loads the core concept (escrow settlement), then the lifecycle, then the action list, then the when-to-use clause, so an agent can stop reading early. It is somewhat verbose with three embedded asides about receipts and portability, but each sentence carries information rather than 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 10-parameter, nested-object, no-output-schema tool, the description supplies the conceptual model and the action-to-intent mapping an agent needs. The per-action parameter bindings rely on the schema hints ('for job', 'for deliver'), and the 'trust' action is only named, not explained, leaving a small gap.

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 the baseline is 3; the description rises above it by giving semantic meaning to the enum values that the schema only lists as bare strings (job=create, deliver=submit and verify, release=accept, refund=reject, verify=check someone else's receipt, trust=reputation). It still doesn't clarify which action consumes which payload fields beyond the schema's own hints.

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+resource (settle a job between two agents through an escrow bridge) and lays out the full workflow from task posting to signed receipt. It is very clear about what the tool does, but it never names or distinguishes itself from its sibling verify_artifact, even though it contains a 'verify' action, leaving the boundary between them unstated.

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?

Provides explicit context for when to use it: 'when an agent takes on paid work, or when you need to prove to a third party that the work was done.' This is genuine usage guidance, but it offers no exclusions and no guidance on when to prefer the sibling verify_artifact, so it stops short of a full when/when-not treatment.

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