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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses that the call is paid ($0.01 USDC via x402), and critically that invoking it returns an HTTP request plus payment requirements rather than the data itself — a two-step flow the agent must understand. Cost and payment mechanics are exactly the kind of behavioral context annotations cannot carry.

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?

Three sentences, front-loaded with the cost and the returned data, then the payment mechanics. Every sentence carries information an agent needs; there is 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 helpfully enumerates what is returned (gas price, latest block, per-transfer ETH cost estimates) and explains the payment round-trip. It could note return encoding or freshness, but for a no-param, no-output-schema tool it is largely complete.

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 tool takes zero parameters, so there is nothing to disambiguate; the baseline for a 0-param tool is 4. The description adds no parameter detail because none is needed.

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 resource and scope: live Base mainnet gas price in gwei, latest block, and ETH cost estimates for USDC (~65k gas) and ETH (21k gas) transfers. This is far more specific than any sibling (e.g. llm_pricing, currency), so an agent can tell exactly what this returns.

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?

It describes the payment workflow ('pay with any x402 client to get the data') but gives no explicit when-to-use guidance or comparisons to alternatives such as llm_cost or currency. Usage is implied by the resource name rather than stated, so it is only minimally adequate.

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