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

No annotations are provided, so the description must carry the full burden. It transparently discloses key behaviors: paid per call with x402 pricing, caching and sharing of answers, block-level freshness, and the credit/reuse model. This far exceeds basic read-tool descriptions.

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 front-loaded with the core purpose and is reasonably concise. The pricing and sharing details add length but are essential behavioral context, so the trade-off is acceptable.

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 adequately specifies the returned fields (name, symbol, decimals, total supply) and also covers the response freshness and network (Base). The additional economic model context makes the tool's behavior fully understandable.

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 input schema fully describes the single address parameter, including pattern and purpose. The description adds no additional semantics beyond the schema's 100% coverage, so the baseline of 3 is appropriate.

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 clearly states the tool reads a Base token's name, symbol, decimals, and total supply from a given contract address. It uses a specific verb ('Read') and resource ('Base token'), and this scope distinguishes it from sibling tools like contract_interface.

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 the tool is for looking up token metadata but does not explicitly state when to use it versus alternatives. No exclusions or comparisons to sibling tools are provided, so guidance is only implied.

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