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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely new context: it is "Solana only", it is "Counts only" (no interpretation/handtyped data, GT_NO_HANDTYPED_V1), and it specifies the exact line format returned in lieu of an output schema. It does not discuss permissions, rate limits, or failure modes, but for a read-only counted-stat tool this is a solid addition.

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 purpose is front-loaded, but the body is one run-on sentence whose long inline output template (with unexplained placeholders like {r}, {vs}, {a}/{b}) dominates the text, and the important constraints ("Solana only. Counts only.") are buried at the very end. The template is load-bearing given no output schema, so the size is defensible, but the structure is hard to parse.

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 specialized statistics tool with no output schema, the description does the necessary work: it states the input context, the content of each returned count (creator rugged/launch window, wallet sell-before-rug rate, buy-hold rate, tape range), and the global constraints. An agent can call it correctly and interpret the return; depth of statistical meaning is left implicit but adequate.

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% with only two parameters, each already documented as a Solana base58 value, so the schema carries the load. The description confirms the roles (the wallet being copied, the coin's launch as the reference point) but adds no syntax or format detail beyond what the schema provides.

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 frames the tool as producing the coin creator's counts and the wallet's counts (plus one formatted line) for a given wallet/coin pair, which is concrete and distinguishable in substance from siblings like groundtruth_creator_flag and groundtruth_wallet_record. However, it never uses a clear action verb ('returns'/'gets') and never names a sibling, so the agent must infer the operation from the output list.

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?

"For a copy bot about to follow a wallet into a coin" gives a real when-to-use context, which is better than nothing. There is no when-not guidance and no mention of the single-stat siblings an agent might use instead, so routing must be inferred.

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