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

No annotations are present, so the description carries the full burden. It discloses the per-call cost, the read-only eth_call mechanism, and the fields returned. However, it does not describe error behavior, rate limits, or behavior for non-token or invalid addresses.

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, compact sentence that front-loads cost, scope, returned data, method, and intended use. Every phrase earns its place with no filler.

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 simple one-parameter, no-output-schema tool, the description covers the address target, the retrieved fields, and the use case. The only notable gap is the precise input format for q, which is left vague by both the schema and the description.

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 q parameter has only generic schema text ('JSON or key=value input'), so the description adds useful context by implying a Base token address is expected. But the exact required format—whether an address alone or an object with chain/address fields—remains undocumented. High schema coverage by count gives a baseline of 3.

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 states a specific verb and resource: on-chain ERC-20 metadata (name, symbol, decimals, total supply) for a Base token via eth_call. It clearly distinguishes itself from the sibling tools, which target domains, repositories, and web pages.

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?

Explicitly tells the agent when to use the tool: 'Use to sanity-check a Base token address before interacting with it.' It does not mention exclusions for other chains or token standards, but the 'Base ERC-20' qualifier and sibling context make the intended scope clear enough.

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