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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description does not need to restate safety. It adds useful non-obvious behavioral context: pricing per call, the x-credit-token header option, the free daily call, and that no wallet or API key is required. No contradiction with annotations.

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 contains useful information but is padded with rhetorical framing like 'WHO administers the blocklist that can freeze you?' and 'straight from the registry.' The pricing and header details are valuable, but the overall text could be tighter without losing meaning.

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?

For a single-required-parameter read-only tool with an output schema present, this description is sufficiently complete. It explains what data is read, which sibling it is distinct from, authentication/pricing expectations, and the required input. Minor gaps like exact output shape are covered by the output schema.

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 schema already documents 'address' as 'B20 token address' with 100% coverage, so the description adds little beyond repeating that address is required. This matches the baseline of 3 for high schema coverage; the description does not meaningfully enrich the parameter meaning.

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 and resource: it 'reads WHO administers each active transfer/mint policy (policyAdmin)' and whether control is being handed over or renounced. It also distinguishes itself from b20-control by clarifying this tool queries the Policy Registry rather than the token's own roles, so an agent can tell them apart.

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 gives clear context for when this tool is relevant, noting it is the 'other half' of freeze/seizure authority and contrasting it with b20-control. It does not explicitly list exclusions or say 'use when X instead of Y,' but the alternative is named and the distinction is clear.

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