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

Adds substantial value beyond the annotations: it discloses return contents (exact units, decimals, provenance), negative space ('Does not approve or transfer tokens'), a per-call cost ('0.01 native USDC'), shared pilot limits, and a pinned version. The readOnlyHint=false is reconciled by the paid-call side effect the description itself discloses, so the agent is not misled.

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?

Front-loads the core operation, then the return contract, then the negative guarantee, then cost/limits. Dense and mostly waste-free, though the raw version hash ('253064e6ce6110d8') is provenance noise that adds little for tool selection.

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 usefully specifies what is returned (units, decimals, provenance), and it covers safety and cost. The gaps are the undocumented parameters and the fact that 'pinned block' is never defined or made selectable, but overall it is sufficient to call the tool correctly.

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% for all three required parameters (tokenAddress, ownerAddress, spenderAddress). The description does not explain any of them, so it fails to compensate for the coverage gap; the only available semantics are the self-explanatory property names and the shared address 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 and resource ('Read an ERC-20 allowance on Base') plus a scope qualifier ('at a pinned block'). This is readily distinguishable from siblings like base_token_facts (metadata) or base_uniswap_v3_lp_accounting_audit (LP accounting), which involve different resources and verbs.

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?

Gives clear context for invocation ('before an AI proposes spending'), telling the agent when this read is warranted. It stops short of naming alternatives or stating exclusions, so it falls short of the 5 tier, but the trigger condition is explicit.

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