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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is already covered. The description adds behavioral context beyond annotations: data is rebuilt every 30 minutes, requires min 8 closed positions, and includes pricing details ($0.02 per call, 10 free/day). This is valuable but not exhaustive.

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 description is a single paragraph but is information-dense with no filler. It front-loads the core purpose and includes pricing and refresh cadence. It is slightly long but each sentence 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?

No output schema exists, so the description carries the burden of explaining the return structure. It does so by describing the leaderboard and live feed composition, including sorting and ranking criteria. It covers data freshness, cost, and filter constraints, making it sufficient for an agent to call correctly.

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 50% (window_min and exclude_bots have descriptions). The description explains sort options (PnL, win rate, ROI) and the 'last N minutes' for window_min, but does not clarify the 'limit' parameter beyond 'top 50' implicitly. It partially compensates for schema gaps but not fully.

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 clear verb (leaderboard and live feed) with a specific resource (pump.fun wallets with best realized PnL). It distinguishes itself from siblings by focusing on smart money tracking with realized profit and recent buys, which is unique among the listed 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 description implies usage for tracking profitable pump.fun wallets and their recent token buys, but it does not explicitly mention when to use this tool versus alternatives like pump_pulse or pump_dev. No exclusion or alternative guidance is provided.

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