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

Annotations cover the safety profile (readOnly, non-destructive, open-world), and the description adds genuinely useful context beyond them: it notes the data is on-chain with no indexer needed, and explains the sweep_creator_fee mechanism so the agent understands that a claim only reflects already-swept fees and that pending fees appear in no claim. That is real behavioral insight, not restated 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?

Front-loaded with purpose, then return fields, then mechanics, then routing. The sweep explanation is dense and slightly long, but it carries real meaning and the opening sentences are crisp; only minor tightening is possible.

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 usefully enumerates the returned fields (signature, mint, lamports, timestamp) and explains the sweep semantics. It falls short only on parameter behavior (limit/network) and pagination, which are left unaddressed.

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 only 33%: creator is documented in the schema but limit and network are not, and the description never mentions either. With low coverage the description should compensate, yet it adds nothing about pagination limits, the default/max of 20/50, or network selection, leaving two parameters ambiguous.

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 and resource ('List recent pump.fun fee-claim events for a creator wallet') with clear scope, and explicitly contrasts itself with the sibling pumpfun_watch_claims, so an agent can distinguish them without opening either schema.

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?

Explicitly names the use case ('audit how much a creator has already cashed out') and the alternative ('for only the claims inside a recent window call pumpfun_watch_claims'). Both the when-to-use and the routing condition are stated outright.

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