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

No annotations are provided, so the description carries the behavioral burden. It discloses that the operation is a read and explicitly states the cost and payment method ($0.003 USDC via x402), which is useful. However, it does not mention potential failure modes, authorization requirements, or absence of state changes beyond the word 'Read'.

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 short sentences with no filler. The core operation is stated immediately and the pricing detail is added without bloat.

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 single-parameter read-only tool, the description conveys the token standard, network, and cost. It does not describe the return format, but the tool name and 'Read totalSupply' make the expected result clear enough for a basic 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?

Schema description coverage is 0%, so the description must compensate for the undocumented 'token' parameter. It does so by specifying that the token must be an ERC-20 or ERC-721 contract, giving meaning beyond the raw schema pattern.

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 verb ('Read'), a concrete resource ('totalSupply'), and the contract standards ('ERC-20 or ERC-721') and network ('Base') it applies to. This clearly distinguishes it from sibling tools such as balance, transfer, or contract info 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 when to use the tool: whenever an agent needs the totalSupply of an ERC-20 or ERC-721 contract on Base. It does not explicitly name alternatives or exclusions, but the use case is clear enough for a simple read operation.

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