Get Escrow Info

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

The description explicitly states that the fulfillment key is never returned and only returned on approval, which is a critical behavioral caveat. It also lists all return fields, giving a complete picture of what the caller can expect.

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 and well-structured, with a brief opening sentence, a critical caveat, and a clean bulleted list of return fields. Every sentence adds value and there is no redundancy.

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 simplicity of the tool and the complete schema with an example value, the description provides all necessary context for a caller to understand what the tool does and what it returns. No additional information is needed.

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 does not add any semantic detail about the escrow_id parameter beyond what the input schema already provides. Since schema coverage is 100% and the parameter is a simple identifier, a baseline score of 3 is appropriate.

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 clearly states the tool retrieves metadata about an existing escrow vault, which distinguishes it from creation, confirmation, and other escrow operations. However, it does not explicitly contrast it with sibling read-only tools or specify when to choose this over alternatives, leaving slight ambiguity.

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 implies usage for fetching escrow metadata without side effects, and the explicit note about never returning the fulfillment key provides important guidance. It does not formally state when to use this tool versus other escrow-related tools, but the purpose is clear enough for typical read scenarios.

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