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

With no annotations provided, the description carries the full behavioral disclosure burden. It conveys a read-only metadata lookup and lists the exact properties returned, but it does not mention error behavior for non-ERC-20 addresses, decimal formatting, or how total supply is denominated. This is minimally transparent but not richly detailed.

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?

A single, well-structured sentence front-loads the purpose and then lists the returned fields. There is no filler, redundancy, or unnecessary detail.

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 one-parameter read-only metadata lookup without an output schema, the description states the chain, the token type, and every value returned: name, symbol, decimals, and total supply. The schema supplies the required input format, so nothing critical is missing for correct invocation.

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 schema already documents the single parameter with 100% coverage, including the expected format '0x followed by 40 hex characters'. The description adds no additional parameter semantics beyond the ERC-20 and Base context, which is largely implicit in the schema.

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 identifies a metadata lookup for an ERC-20 token and enumerates the returned fields: name, symbol, decimals, and total supply. It lacks an explicit verb like 'retrieve' or 'get', but the intended operation is unambiguous and distinguishable from siblings such as token_balance.

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 provides no guidance on when to use this tool versus address_report, gas_now, token_balance, or tx_status. The only context is the 'Base' chain, which is a scope cue rather than an alternative-selection rule.

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