get_escrow_status

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

The description adds a behavioral trait: it automatically detects expired escrows. However, with no annotations provided, it does not disclose whether the tool is read-only or requires specific permissions, leaving some behavioral ambiguity.

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?

The description is concise with a clear structure: purpose, output details, behavior note, and parameter explanation. No redundant 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?

Given the simple tool with one parameter and no output schema, the description adequately covers what the tool returns and a key behavioral aspect. It could elaborate on the response format, but the listed output items suffice for usability.

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?

The description includes an Args section for the escrow_id parameter with an example format ('escrow_abc123def456'), which adds meaningful context beyond the schema's minimal title. Schema description coverage is 0%, so the description compensates well.

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 explicitly states it returns the current status and all details of an escrow, including specific items like amount, parties, deadline, risk score, and payout details. This clearly distinguishes it from sibling tools like create_escrow or list_escrows.

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 description describes what the tool does but does not provide explicit guidance on when to use it versus alternatives, nor does it state exclusion criteria. The usage is implied for retrieving a single escrow's details.

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