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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the description's 'without moving funds' largely restates the safety profile. It does add the useful notion that the response reports 'blockers', but says nothing about state freshness, chain confirmation requirements, or rate limits.

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?

A single front-loaded sentence with no filler. The trailing 'without moving funds' is mildly redundant against destructiveHint=false, which keeps it from a 5.

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 with full annotation coverage and no output schema, naming both returned concerns ('readiness' and 'blockers') gives the agent enough to call it correctly. Greater detail on what constitutes readiness (balance thresholds, approvals, chain state) would help interpret results but is not required to invoke it.

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?

Zero declared parameters, so the baseline of 4 applies. The only wrinkle is the permissive 'additionalProperties: {}' in the schema, which the description does not address, but there is no parameter semantics to explain.

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 ('Read') and a specific resource ('Base USDC escrow readiness and blockers'), plus a scope qualifier ('without moving funds'). It is distinguishable from most siblings, though it does not explicitly distinguish itself from the similarly-shaped check_agent_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?

Usage is only implied by the word 'readiness' – the reader infers this is a pre-flight check before escrow-dependent actions. There is no explicit when-to-use, no exclusion, and no pointer to which sibling to use instead for agent-side readiness.

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