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

Adds real behavioral context beyond annotations: a hard cost of 0.01 native USDC on Base and that the read is pinned to one block (deterministic snapshot). Annotations cover openWorldHint and destructiveHint=false, and the payment requirement explains why readOnlyHint is false. It stops short of describing rate limits, failure/refund behavior, or output format.

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 dense sentences with the core capability front-loaded and the cost/disclaimer trailing. Every clause carries information; 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?

With no output schema, the description takes on the burden of describing returns and does so by naming the four payload fields, plus discloses cost and a determinism guarantee (pinned block). It omits return shape/format and error conditions, which keeps it short of a 5.

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 100% for the single tokenAddress parameter, so the schema already carries the semantics (Base mainnet ERC-20 contract address, 0x + 40 hex pattern). The description only implicitly scopes the input to Base ERC-20 tokens, which is a marginal addition. Baseline 3 is correct.

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 and resource ('Read a Base ERC-20 fact packet') and enumerates exactly what the packet contains (metadata, supply, bytecode hash, EIP-1967 slot), which implicitly separates it from siblings like base_token_allowance and the LP accounting audit. An agent can tell what this returns without opening the schema.

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?

Usage is only implied by the resource description; there is no explicit when-to-use, when-not-to-use, or routing to sibling tools such as base_token_allowance. The stated 0.01 USDC prerequisite is a useful precondition but is not guidance on selecting this tool.

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