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

Annotations already declare this tool read-only and idempotent. The description adds useful operational context: it uses eth_getCode and nonce, and is preflighted so users do not pay during an RPC outage. No contradiction with annotations.

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 dense sentences: the first front-loads the functional outputs, the second adds the important preflight behavior. No filler or repetition.

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?

With one well-documented parameter, an output schema, and annotations covering read-only/idempotent behavior, the description covers scope, method, heuristics, and outage-related safeguards. Nothing essential is missing.

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 single parameter is fully documented in the schema with format details ('EVM address, 0x-prefixed'). With 100% schema description coverage, the description does not need to add parameter-level semantics beyond what already exists.

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 resource (EVM address) and concrete outputs: total outbound transaction count, contract check via eth_getCode, and a first-funded heuristic. This clearly distinguishes it from sibling balance/validation tools.

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 use for on-chain activity snapshots, but it does not explicitly state when to choose this tool over sibling tools like balance_check or erc20_balance. No alternatives or exclusions are named, so routing must be inferred from the described outputs.

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