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

Beyond the annotations (readOnlyHint, idempotentHint, openWorldHint, non-destructive), the description adds valuable behavioral detail: stablecoin variants return no-rebase, the call is priced at $0.02 over x402 on Base, prepaid headers are supported, a free daily call exists, and no wallet or API key is required. This gives the agent concrete invocation and cost expectations.

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 then covers input, edge-case behavior, network, pricing, and auth in a compact block. The pricing and header details are slightly verbose for a tool description, but they earn their place because they are important for correct invocation.

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?

This is a single-parameter read-only tool with an output schema, and the description covers all essential context: what it reads, what it flags, stablecoin edge case, required input, network/chain, cost, billing options, and authentication. Nothing an agent needs to call it correctly is missing.

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%, so the schema already fully documents the single 'address' parameter as a B20 token address. The description adds the 'Asset-variant' context and the stablecoin caveat, but does not add meaningful parameter format or validation details beyond the schema.

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 uses a specific verb ('Reads') attached to a clear resource ('B20 Asset token's rebase multiplier'), and adds the risk-flagging intent. It also distinguishes stablecoin behavior explicitly, which separates this tool from related B20 variants.

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 conveys when to use the tool: to check whether an issuer-controlled rebase is invisibly scaling balances, and it notes that stablecoin variants return no-rebase. It does not explicitly name alternative sibling tools, but the context is clear enough for an agent to select it for this read-only rebase risk query.

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