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

Annotations already carry readOnly=false, idempotent=true, destructive=false, but the description adds meaningful beyond-annotation traits: the tool is monetized ($0.25 USDC via x402), payment networks are specified (Base or Arbitrum One), and the persistent effect is disclosed (retired ID reports revoked on every later check). It stops short of describing failure/error behavior or explicit irreversibility, which is why it is a 4 rather than a 5.

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?

Four tight sentences, each earning its place: purpose+requirement, persistent effect, monetization+endpoint+pricing. The purpose is front-loaded and there is zero filler, making it easy for an agent to extract the critical call facts quickly.

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 values need not be described in prose. The description covers the essential operational facts an agent needs before calling: authentication requirement, payment amount and network, the persistent consequence, and the endpoint. The notable gap is the unresolved parameter-semantics gap for required fields, which keeps this below a 5.

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 only 20% — only agent_wallet is documented. The description partially compensates by explaining the provenance of revocation_signature (from accountable principal or Embassy) and the payment context of the tool, but it adds nothing about agent_id, reason, or idempotency_key. With low schema coverage, the description must carry more weight and it does not.

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 opens with a specific verb-resource pair, "Retire an Agent ID instantly," which unambiguously states the operation. It also distinguishes itself from lifecycle siblings (agentid_issue, agentid_renew, agentid_verify) because retire/revoke is a distinct phase, and the signature-requirement clause adds scope precision.

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 implies usage context (retire an Agent ID within a lifecycle) and states the prerequisite for legitimate use (signature from accountable principal or Embassy for cause), which is useful. It never names sibling alternatives or says when NOT to use this tool, leaving the agent to infer the revoke-vs-renew/verify choice.

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