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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real context beyond that: the claim happens via a claimUrl the user signs in their own wallet, and Moonlauncher charges nothing for claims.

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 dense sentences, front-loaded with the read-only status and the core value, with no filler. Every clause (scope, claimUrl, wallet/launchId, fee policy) carries information an agent needs.

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?

There is no output schema, so the description responsibly names the key returned elements (claimable amount across coins and a claimUrl). It could be more explicit about the full response shape, but no essential calling information is missing.

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%, so the baseline is 3, but the description adds the mutual-alternative semantics the schema does not express: wallet and launchId are two ways to identify the same creator wallet. Format hints (base58, lch_ prefix) remain in the schema.

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 read operation: how much pump.fun creator fee income a wallet can claim across every coin it created, plus a claimUrl. The resource and scope are unambiguous, though explicit differentiation from token_info and launch_status siblings is absent.

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?

Gives clear usage modes: pass the creator's wallet, or pass a launchId from launch_token to resolve that launch's wallet. It does not state when-not to use the tool or name a competing alternative, so it stops short of a 5.

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