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

With no annotations, the description carries the full burden and does well: it discloses the returned fields, the supported chains (Base/Polygon/Solana), and the cost floor ('From $0.005 USDC'). It does not explicitly state read-only semantics, auth requirements, or failure modes, but the enumerated behavior is unusually complete for a bare definition.

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?

One dense, front-loaded sentence that leads with the resource and name, then layers output fields, chains, and price. No filler, though the stacked clauses make it slightly dense.

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 single-param read with no output schema and no annotations, the description covers what it returns, which chains it supports, and its cost – enough for an agent to call it correctly. Minor gaps remain around return format and failure handling.

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 coverage is 0% and the single 'address' param has no schema description, but the description compensates partially by stating the input is 'a wallet or contract,' clarifying that the address may be either an EOA or a contract. It adds meaning beyond the bare string type but not format/chain-specific detail.

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+resource ('reliability read for a wallet or contract') and enumerates the exact output fields (exists, has code, nonce, native balance, 0-100 score with reasons), so an agent knows what it produces. It does not differentiate itself from close siblings like risk_check, trust_check, or wallet_security, so it stops short of a 5.

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 'Pre-payment reliability read' framing implies a usage context (before paying) but never states when to prefer this over risk_check, trust_check, or should_pay, nor any exclusions. Usage is only implied, matching a 3.

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