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

No annotations are present, so the description carries the behavioral disclosure burden. It does state that the operation is a read and lists the returned fields, but it does not mention failure modes such as non-ERC-20 addresses or tokens missing the decimals method. This is minimally transparent but incomplete.

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?

The description is a single sentence with no filler, front-loading the core action and resource before listing the additional outputs. Every word contributes useful information.

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 tool, the description names the input, network, and expected output fields, which is mostly sufficient for invocation. However, with no output schema and no annotations, it leaves the exact result shape and edge-case behavior unspecified, such as how a missing decimals value is handled.

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 only provides an address pattern for 'token' with no description, so the description must compensate. It frames the parameter as an ERC-20 token on Base whose total supply is read, clarifying both the input context and what will be returned. It stops short of explicitly saying 'token is the contract address', but the schema pattern and wording make that evident.

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 uses a specific verb ('Read'), names the exact resource ('ERC-20 total supply'), and identifies the network ('Base') plus the accompanying outputs. This clearly distinguishes it from sibling tools like base_erc20_balance and base_erc20_allowance.

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 imperative phrasing 'Read an ERC-20 total supply on Base' gives clear context for when the tool should be selected. It does not explicitly mention alternatives or exclusions, but the resource and network are specific enough that an agent can route to it without confusion.

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