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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context beyond annotations: it is a paid call ($0.005 per call, 10 free/day), combines launch history with trading profile, and produces a risk level and reasons. No contradictions with 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?

Three sentences with no redundancy: purpose and verdict categories, method and data sources, and pricing. The most important information is front-loaded, and every sentence earns its place.

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 single-parameter, read-only tool with no output schema, the description covers purpose, trigger condition, data sources, output summary (risk level and reasons), and cost. It does not specify the exact response format, but that is acceptable given the tool's simplicity and the annotations already covering safety. Slight gap: no explicit comparison to overlapping siblings, though purpose clarity mitigates this.

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% and the parameter is already documented as a 'wallet address' with a validation pattern. The description adds that the wallet is Solana-specific, which is minor additional context, but provides no new format or constraints beyond the schema. Baseline 3 applies because the schema carries the parameter meaning.

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 'One-call verdict on a Solana wallet before you deal with it' and enumerates concrete verdict categories (serial token launcher, fast dumper, trading bot, or clean). It also names the two data sources (pump.fun launch history and trading profile), making the tool's purpose specific and distinguishing it from siblings like wallet_holdings or price.

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 phrase 'before you deal with it' gives a clear usage trigger and context. However, it does not explicitly name alternatives or exclusion conditions, such as when a simpler tool like price or pump_wallet would be more appropriate. This is clear context but lacks comparative routing.

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