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

No annotations are supplied, so the description carries the full load, and it does disclose two things annotations could not: that it is a non-mutating verification and that each call costs 0.002 USDC over x402 on Base or Solana. The cost metering is a genuinely useful behavioral disclosure. Gaps remain around chain defaulting and failure modes for malformed addresses.

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?

Two sentences, front-loaded with the purpose and checks, with pricing and motive trailing. No filler and no restatement of the tool name.

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 2-parameter tool with no output schema, the description usefully enumerates the returnable signals (EOA vs contract, code size, tx count, balance, burn detection) so the agent knows what comes back. The payment context is covered too. Only the chain-handling semantics and error behavior are left unaddressed.

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 100%, so the baseline is 3. The description adds no meaning to 'chain' beyond the schema's thin 'Example: base' — it does not say which chains are supported, whether chain defaults, or that the same address format applies across chains, which is the one ambiguity an agent would hit here.

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 opens with a specific verb-and-resource pairing ('Recipient pre-flight check' ... 'verifies whether an address is an EOA or contract') and enumerates exactly what is checked: code size, tx count, native balance, and burn/zero-address detection. That is far more specific than a tautology. It falls short of a 5 because it never names the neighboring tools it overlaps with (evm_balance, evm_contract, evm_token_balance), leaving the agent to infer why a composite check is preferable.

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?

It gives an explicit use window — 'before transfers or payouts' — and a concrete motive, 'Use it to prevent burning funds'. What is missing is the negative case: nothing says when this is unnecessary (e.g. already-known addresses) or that evm_balance/evm_contract should be used when only one datum is needed.

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