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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds real context beyond them: the pricing model ($0.03/call over x402 on Base), the prepaid x-credit-token header for unlimited calls, the absence of a free tier, and no API key requirement. These are operationally decisive details an agent cannot get from structured fields.

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 and the structure is logical (what it does, the vector, the inputs, the pricing). It is somewhat dense and marketing-flavored with em-dash asides, but each sentence carries information rather than 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?

An output schema exists so return format needn't be explained, and rich annotations carry the safety profile. The description also covers payment and access requirements. It is close to fully self-sufficient; only explicit sibling routing 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?

There is a single required parameter with 100% schema coverage; the schema already documents 'address' as the B20 token address, and the description only restates 'Required input: address.' No format or syntax is added, so the baseline 3 applies.

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 ('reads the token's full policy/pause event timeline plus the live policy state') and a distinct outcome ('tells you if — and exactly WHEN — it turned seizable'). This is clearly separable from siblings like b20_freeze_check, b20_seizure_history, and b20_policy_admin without opening any 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?

Gives a clear scenario framing: 'Did this token BECOME seizable after launch?' and names the threat model it addresses (the B20-only rug vector). However, it does not explicitly state when to prefer this over b20_seizure_history or b20_freeze_check, leaving sibling routing to inference.

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