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

With no annotations, the description carries the burden of disclosing side effects. It explicitly states 'without moving funds', which provides a key non-destructive guarantee. However, it does not detail error cases, authorization requirements, or the exact semantics of 'readiness' and 'blockers'.

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 one concise sentence, front-loaded with the action and object, and contains no waste or 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?

For a zero-parameter read-only tool, the description conveys the core function and a key behavioral guarantee. It hints at the return content ('readiness and blockers') though it does not detail the output format. Given the low complexity and lack of output schema, the description is sufficiently complete.

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 tool has zero parameters, and the schema is empty. The description adds no parameter-specific information, but no parameters exist; baseline 4 applies.

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 uses the specific verb 'Read' and clearly identifies the resource ('Base USDC escrow readiness and blockers'), with a scope ('current') and a safety qualifier ('without moving funds'). It distinguishes from sibling tools like check_agent_readiness by focusing specifically on escrow readiness.

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 a use case: checking current escrow readiness before any fund movement. However, it does not explicitly cite alternatives or exclusions, such as 'use check_agent_readiness for agent readiness', so it falls at implied usage rather than clear guidance.

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