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

The description transparently discloses generation and secret key handling, but it contradicts the annotation 'readOnlyHint: true', as generating a keypair is a write operation. Per scoring rules, contradiction leads to score 1.

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?

Three sentences, front-loaded with purpose, no waste. Every sentence adds essential information.

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 are covered. However, missing details on maxAttempts behavior, error states, and case sensitivity handling leave some gaps for a tool with 4 parameters.

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 50%, and the description only mentions prefix/suffix without adding details on maxAttempts or caseSensitive. It does not compensate for the missing parameter information.

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 clearly states 'Generate a Solana keypair whose address ends/starts with a vanity pattern' with specific verb and resource, and distinguishes from siblings as no other tool generates vanity addresses.

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?

Provides explicit guidance: 'Caller must save the secret key immediately — it is never stored' and mentions a hard timeout of 60s, but does not explicitly state when not to use the tool or compare with alternatives.

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