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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: it is free (cost), spans 'supported launchpads' (coverage), and targets 'unswept or unclaimed' fees (definition of results). It does not describe the return format, but for a read-only scan the addition is modest.

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?

Two short fragments with zero waste, and the key benefit ('Free') is front-loaded before the purpose. It is efficiently sized for a single-parameter read tool, though very terse.

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 one-param, no-output-schema tool the description is close to adequate, but with no output schema it stops short of indicating what the scan returns. It also leaves 'supported launchpads' undefined, so an agent cannot fully anticipate scope or result shape.

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 0% and the single 'wallet' parameter is undocumented in the schema. The phrase 'one-wallet scan' weakly signals that a single wallet is the input, but it adds no format, chain, or address-syntax meaning beyond what the schema already implies.

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 ('scan') and resource ('launchpad creator fees') with a clear scope ('one-wallet'). It is unambiguous what the tool produces, though it does no explicit sibling differentiation (none of the siblings overlap with this domain, so that omission is low-cost).

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?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. 'Free' is a cost signal, not usage guidance, so an agent is left to infer intent from the purpose line alone.

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