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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: it specifies that a thin record of one or two settled launches is reported as unreadable, that the funder rule's verdict is quoted verbatim with its scoring date, and that no record is not a clean record. It also states the base58 case-sensitivity failure mode, which is genuine behavioral disclosure an agent cannot infer.

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?

The caveat block (negative screen, not a score, survival is a low bar, thin records) earns its place, but the first sentence is a single run-on spanning roughly a hundred words, and the case-sensitivity warning appears twice in the description and again in the schema. Useful content, poor structure and noticeable redundancy.

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 no output schema, the description carries the return burden itself and does: it enumerates each section of the record, states how the funder verdict is quoted, and flags the thin-record edge case. An agent has enough to call it correctly and to set a user's expectations about interpretation.

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 schema already states "base58 Solana wallet address, exact case" plus the lowercasing consequence. The description's case paragraph repeats that same information rather than adding syntax, format, or validation detail beyond the schema, so the baseline 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?

The opening names the resource (a Solana token creator wallet) and enumerates the record's contents: settled launches, indexed launches newest-first, launch cadence, and the first-transaction funder. It references the sibling solana_deployer but only as "the same screen ... with the same measured worth," which tells an agent they overlap without clarifying how they differ, so the sibling differentiation is only partial.

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 "Call this when a user asks..." sentence gives four concrete trigger conditions covering launches, activity level, volume-launching, and funder provenance. There is no explicit when-not or a clear routing rule against solana_deployer, which keeps it out of 5 territory.

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