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

Annotations already declare readOnly, idempotent, openWorld and non-destructive. The description adds genuinely non-obvious operational context: p pricing at $0.04/call over x402 on Base, a prepaid x-credit-token header for unlimited calls, no free tier, and no API key required. It adds no detail about the response shape, but that is covered by the output schema.

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?

Every sentence carries information (purpose, sibling differentiation, pricing), but the leading rhetorical question ('WHO administers the blocklist that can freeze you?') and the repeated 'other half of who can freeze/seize you' framing are stylistic padding for a one-parameter read tool. Front-loading is good, but the phrasing is heavier than needed.

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 not be described, and the annotations cover the safety profile. The description supplies purpose, sibling routing, input requirement, and pricing/auth mechanics, so an agent has what it needs; only the near-sibling differentiation among b20_policy_watch/policy_members is thin.

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% for the single 'address' parameter, so the schema already carries the semantics. The description only restates 'Required input: address' and does not add format or source hints (e.g. that it should be the B20 token address) beyond what the schema provides. 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+resource: it reads who administers each active transfer/mint policy (policyAdmin), pending handover (pendingPolicyAdmin), and renouncement status, straight from the Policy Registry. It explicitly distinguishes itself from b20-control ('reads the token's own roles') and from the registry-based control angle, so an agent can tell it apart from the many b20_* siblings.

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 clear context: this is the complement to b20_control for the 'who can freeze/seize you' question, and it must be sourced from the Policy Registry rather than the token itself. It doesn't explicitly rule out or route away from near-neighbors like b20_policy_members or b20_policy_watch, so it stops short of full when/when-not guidance.

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