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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=false, so the safety and repeat-call profile is covered. The description adds the polling/batch context ('after a delay'), but it is ambiguous about whether the tool blocks or streams, and says nothing about return volume or pagination. Useful but thin beyond the 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?

Two sentences, zero filler, with the core behavior front-loaded and the routing hint second. Every clause earns its place.

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 carries the burden of describing what comes back; 'all fee-claim events' is minimal and leaves fields, ordering, and volume unknown. The polling semantics of a 'watch' tool are also left implicit. Adequate for routing, incomplete for invocation detail.

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 67%: creator and durationMs are documented in the schema (including the default and 1800000 ms cap), while network has only an enum and default. The description names durationMs and its role, but adds no format or semantics beyond what the schema already states, 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?

States a specific verb and resource: 'Return all pump.fun fee-claim events for a creator wallet.' The scope qualifier ('within a look-back window') plus the explicit contrast with pumpfun_list_claims lets an agent separate this from its nearest sibling 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?

Gives both a positive condition ('use this for batch collection after a delay') and a named alternative with the condition that selects it ('for a creator's full recent claim history call pumpfun_list_claims'). This is the explicit when/when-not/alternative pattern.

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