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

Annotations only provide hint flags; the description adds meaningful behavioral context: the operation is paid ($25.00 USDC), rate-limited (10/day/wallet, 2/hour/IP), and produces an exclusive, permanent wallet. It does not cover failure modes or the actual charging flow, but it goes well beyond the structured 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?

Four short sentences, each carrying essential information: the action, uniqueness guarantee, usage limits, and price. No filler or redundant restatement of the schema.

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 one parameter, an output schema, and annotations, the description covers purpose, price, rate limits, and persistence semantics. The only notable omission is how/when the $25 payment is actually charged, which is secondary to correct invocation since the caller already provides the paying wallet address.

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 coverage is 100% and the single 'wallet' parameter already has a description and format validation ('42-char hex'). The tool description adds no further parameter-level meaning, so the baseline score of 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: 'Generate a fresh permanent EVM wallet.' Additional attributes ('Zero-balance verified, single-use (yours permanently)', '$25.00 USDC') make it clearly distinct from the plaza.* registration/badge 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?

The description clearly implies when to use it—whenever a new permanent EVM wallet is needed—and includes rate limits and cost. However, it does not explicitly contrast with any sibling tool or state when not to use it.

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