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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds valuable domain behavior beyond annotations: the shared RevenueManager balance across launched tokens, the roughly 0.001 ETH payout threshold, and why pendingInPool can grow while claimable remains zero.

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 core return value is front-loaded and every clause carries domain-relevant information. It is somewhat dense as a single long sentence, and 'Read-only' repeats the annotations, but there is no significant filler.

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 read-only tool with no output schema, the description explains the key concepts and mentions pendingInPool, but it does not fully specify the response shape, units, or whether pendingInPool is per-token or aggregate. It is adequate but leaves clear interpretive gaps.

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 100% and the sole wallet parameter is already documented as 'Creator wallet.' The description reinforces that this wallet is the creator whose launched tokens are queried, but it adds little parameter-specific detail beyond 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?

The description states a very specific resource: a wallet's claimable ETH from swap fees for tokens launched through CoinFactory, plus pending Flaunch pool fees. This is clearly distinguishable from sibling token, market, and transaction-building tools.

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 read-only nature and reward-focused output imply when to use it, but the description does not explicitly name alternatives such as build_claim_rewards_transaction or describe when not to use it. Usage is inferable rather than stated.

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