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

This goes well beyond the annotations. It discloses the 10-call rate limit, the release_deadline window, that checks run on the output payload, that auto_release releases the escrow in the same call, and the 501 feature_unavailable gating under ESCROW_API_ENABLED. These are exactly the side effects and failure modes an agent needs before calling a write tool.

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?

Four short sentences, each carrying a distinct constraint: eligibility, limits, side effect, and gating error. Preconditions and limits come first, with no filler or repetition of the title.

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?

With no output schema, the description usefully explains what the escrow does with the submission and what auto_release triggers. It does not explain what a failed check returns or the point of the 'note' field, which are the remaining gaps for a three-parameter mutation tool.

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 33%, with only 'output' documented as any JSON up to 512 KiB. The description clarifies that the escrow's checks are run against 'output', which adds meaning, but the 'note' parameter is undocumented in both schema and description, leaving a gap it does not compensate for.

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 gives a specific verb+resource ('Submit a deliverable or proof to an escrow') and adds role and scope constraints. It does not, however, distinguish the tool from the sibling 'submit_deliverable', which an agent could easily confuse with it.

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 states clear preconditions: payee only, before release_deadline, at most 10 submissions, and requires can_submit_deliverables. What is missing is explicit routing guidance relative to the similar sibling submit_deliverable, and what to do after a failed check (for example, request_revision).

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