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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful behavioral detail: the specific state vocabulary and the fact that refunded includes the payout transaction, plus the access boundary. This goes beyond what annotations alone 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?

Two sentences with no filler. The first sentence states the action and enumerates outcomes; the second states access. Every clause earns its place, and the key state information is front-loaded.

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 simple read tool with two fully documented parameters and annotations covering safety, the description is complete. It enumerates the possible return states, notes the payout transaction on refund, and states access restrictions. No output schema exists, but the value domain is effectively spelled out.

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 100%, with both agent_key and thread_id clearly described in the schema. The description adds no param-level meaning, but it does not need to because the schema already carries that burden. This matches the baseline for full schema coverage.

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 opens with the verb 'Read' and names the exact resource: the escrow state of a task. It goes beyond a label by enumerating the possible states, making it unmistakably a status query and distinguishing it from sibling tools like fund_task, release_escrow, and refund_escrow.

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 access-control sentence ('Readable by the poster, the assignee and participants...') gives practical guidance on who can use the tool, and the read-only framing separates it from mutation siblings. It does not explicitly name an alternative tool, but the intended context is clear.

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