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

No annotations exist, so the description carries the full burden: it discloses the exact fields returned, frames the operation as an information read, and states the price ($0.001 USDC), which is behavior an agent cannot get from the schema. It omits whether the call is cached, rate-limited, or what happens when the chain is unknown, which keeps it short of a 5.

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 covers purpose and payload, followed by a one-line use case, a call example, and the price. Every clause carries information; nothing is repeated from the schema.

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 no output schema, the description correctly enumerates the return fields, and it adds cost and a canonical use case for a simple one-parameter read tool. The remaining gap is the absent list of valid chain identifiers and default-chain behavior, which an agent would need to call it reliably.

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%, so the description must compensate for the single `chain` parameter. The inline example `{chain:"base"}` usefully demonstrates the value format (a lowercase chain slug), but supported values and the default behavior for this optional parameter are never stated.

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?

"EVM network info in one call" names a specific resource and the enumerated payload (chain ID, client version, block height, head age, gas price, base fee, native symbol) makes the aggregate scope unmistakable. This clearly separates it from narrow siblings such as chain_chain_id, chain_block_number, and gas_fees.

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?

"Confirms which chain an RPC is on before signing" gives a concrete pre-flight use case rather than leaving usage implied. It stops short of explicitly routing the agent away from chain_chain_id or gas_fees when only a single field is needed, so it is strong context but not full when/when-not guidance.

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