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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes beyond them with real operational context: $0.04 per call over x402, an x-credit-token header for unlimited calls, no free tier, and no API key. It also discloses what it actually inspects on chain (transfer-policy admin), which the annotations do not cover.

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 core question is front-loaded, which is good, but the body is padded with promotional copy ('— Live —', 'all 13 Coinbase equities, and the next on day one') and crowded pricing/header sentences that could be trimmed. Several clauses serve marketing rather than agent decision-making.

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 an output schema present, return values need no explanation, and the annotations cover safety semantics. The description still supplies the missing pieces an agent needs – what powers are read, the verdict scale, cost, and auth – making it nearly complete for a single-parameter read tool.

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 coverage is 100% and the single 'address' parameter is documented in-schema, so the baseline is 3. The description only restates that 'address' is required and adds no format, chain, or validation nuance 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 states a specific verb+resource: it reads a B20 token's protocol-level freeze/seize/mint powers (Policy Registry, burnBlocked) into a single hold/caution/avoid verdict, and clarifies scope by distinguishing a genuine tokenized stock from an equity-ticker impostor. It never names the many nearby siblings (b20_freeze_check, b20_control, b20_guard, token_risk), so differentiation is left implicit.

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 implied by the framing (assess whether a B20 token can freeze/seize funds) and the required 'address' input is stated, but there is no explicit when-to-use/when-not guidance and no routing to alternatives despite seven-plus overlapping b20_* and risk siblings. An agent must infer the trigger condition.

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