escrow__escrow_status

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

With no annotations, the description should disclose behavioral traits. It does not mention that this is a read-only query, authentication requirements, or any side effects. The prefix about exactly-once settlement is generic and not specific to this tool.

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 short but overly terse; it sacrifices clarity for brevity. The prefix adds module context but does not describe the tool's function. Structure is minimal and unhelpful.

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 no output schema, the description should hint at the response structure. 'Current record' is too vague; it does not specify what fields are returned or if pagination applies. The tool is critically under-described.

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 schema has 0% coverage for parameter descriptions, and the tool description does not explain what escrow_id is or how to obtain it, leaving the agent without necessary context for invocation.

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 'Current record for an escrow' is vague and does not explicitly state that the tool retrieves the status of an escrow. It lacks a verb and fails to distinguish from sibling tools like escrow__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?

No guidance is provided on when to use this tool versus alternatives such as escrow__list_escrows or other escrow-related tools. The agent receives no context for decision.

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