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

Annotations already cover read-only and open-world behavior; the description adds a pricing/quota model, a hard failure mode (missing decimals() is an error, never assumed), and bytes32 edge-case handling. The only gap is that the single-block read guarantee is largely repeated from the schema's block parameter, not extended.

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?

Dense and nearly waste-free, with the failure-mode and bytes32 notes earning their sentences. The pricing bracket leads, which slightly delays the core purpose statement that would be better front-loaded.

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?

There is no output schema, so the description correctly enumerates the return fields and discloses the error condition for tokens without decimals. Chain and token validation rules live in the fully-covered schema, so nothing an agent needs to call it safely 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?

Schema description coverage is 100%, so the baseline applies: chain format, token checksum requirement, and block values are all already documented in the schema. The description adds nothing beyond echoing that all values are read at one block.

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?

Names a specific resource (ERC-20 token metadata) and enumerates exactly the fields returned: name, symbol, decimals, total supply, read from the contract at a single block. That enumeration distinguishes it from siblings like token_price, evm_balance, and evm_contract_type without any guesswork.

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?

Gives useful operating context (pricing tier, bytes32 handling, and that missing decimals() is an error rather than defaulted) but never says when to pick this over token_amount_convert, token_price, or evm_contract_type. Usage is implied by the enumerated return fields rather than stated.

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