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

With no annotations, the description carries the full behavioral burden, but it only implies a creation operation. It omits critical traits for a financial escrow tool: whether funds are locked, authorization requirements, reversibility, how the nested 'conditions' object affects release, and any side effects. It provides only the most basic action type.

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 a single short phrase, not verbose, but it is critically under-specified for the complexity of the operation. Conciseness here reflects under-specification rather than efficiency; no structural elements like clauses or lists help an agent.

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 complex financial escrow creation tool with 5 parameters, a nested 'conditions' object, no output schema, and no annotations, the description is completely inadequate. It omits prerequisites, behavior on success/failure, return information, and parameter guidance.

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 0% across 5 parameters (payer_id, payee_id, amount, currency, conditions), and the description adds no meaning about their formats, roles, or constraints. It does not compensate for the total lack of schema documentation.

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 ('Create') and resource ('agent-to-agent escrow'), clearly distinguishing it from sibling escrow operations like escrow_release and escrow_dispute. An agent can identify the operation without opening the schema.

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?

No guidance on when to use this tool versus escrow_release, escrow_dispute, or other defi tools; no prerequisites or exclusions are mentioned. The description merely states the action, leaving the agent to infer context.

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