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

Annotations already declare a safe read, and the description adds real behavior beyond them: authorization scoping (payer/payee only) with the exact 404 outcome, plus a feature-flag gate that produces 501 with a named error code. That is exactly the error/auth context an agent needs before calling.

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 short sentences, front-loaded with the purpose and followed by the two failure conditions. No filler, though the gating sentence is slightly terser than it could be about what the flag state means for callers.

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 one-parameter read tool with no output schema, the definition covers purpose, authorization, and availability gating. It omits nothing an agent needs to attempt the call correctly; the return payload shape is out of scope absent an output schema.

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?

There is a single required parameter, escrow_id, with 0% schema description coverage, so the schema alone gives no elaboration. The description does not describe the identifier's format or provenance, but the name is self-evident and needs little gloss.

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 ('Get a stand-alone escrow') and the 'stand-alone' qualifier distinguishes it from the sibling get_escrow. It never explicitly contrasts with that sibling, but the qualifier carries the differentiation.

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?

Gives concrete selection/eligibility conditions: only payer and payee can call it, anyone else gets 404, and it returns 501 feature_unavailable while ESCROW_API_ENABLED is off. It does not explicitly say when to prefer get_escrow instead, which keeps it from a 5.

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