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

Even with annotations present (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description adds exceptional behavioral detail: it returns an unsigned transaction and a short-lived voucher, never signs or holds keys, requires the user to approve and send, warns the transaction cannot be undone, and discloses the already-claimed ineligible state. This far exceeds what the annotations convey and covers security-critical behavior. No contradiction with annotations found — readOnlyHint=false is consistent with the stateful voucher issuance described.

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?

Despite being multi-paragraph, every sentence carries unique information: the no-sale clarification, the on-chain amount workaround, the one-per-wallet retry warning, and the unsigned-transaction security model. It is front-loaded with the core purpose and each subsequent clause prevents a distinct potential misuse. There is no filler or repetition of what the schema already states.

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 security-sensitive tool with no output schema, the description is fully self-sufficient. It specifies exactly what is returned (eligibility, transaction count, transaction, voucher), what is deliberately not returned (the claim amount, with an on-chain alternative), and the irreversibility and signing requirements. Given the tool's complexity, nothing an agent needs to call it correctly 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?

The single address parameter is already fully documented in the schema (100% coverage with format and pattern). The description adds value beyond the schema by contextualizing what the address must satisfy — the 167+ transaction threshold on Base mainnet — and clarifying the address is expected on Base mainnet. It doesn't add syntax details, but the eligibility context enriches the parameter's meaning beyond mere format.

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 precise verb-resource pair ('Check whether a wallet can claim BASE167') and immediately distinguishes the tool by explaining the unique claim model — no sale, no presale, no allocation, only wallets with 167+ Base transactions. This clearly differentiates it from the sibling claim and enrollment tools by framing it as an eligibility check rather than a claim or setup action.

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 strong usage context: use it to determine eligibility, and read calculateReward(claimCount()) on-chain for the claim amount rather than relying on this tool. It also states explicit exclusions — 'never treat a refusal here as a reason to retry' and the one-claim-forever rule. It stops short of naming a specific sibling alternative to prefer, but the when-to-use and when-not-to guidance is largely explicit.

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