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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context beyond annotations: the exact contents of the returned report and the explicit statement that results are historical facts with no forecasting or advisory component. It does not say what happens for an address that is not among the measured operators.

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 compact sentences: the payload comes first, the scope disclaimer second. The metric enumeration is dense but every item corresponds to actual returned data, so nothing is wasted.

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?

With no output schema, listing the metrics is necessary and done well, and annotations cover safety. However, the description leaves open the overlap with botsharper_check_wallet and says nothing about behavior for addresses outside the measured population or about error/empty results, which matters for a single-address lookup tool.

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% for the single 'address' parameter, so the schema already carries the base58 format detail. The description adds only the qualifier 'public' Solana address, which is marginal. Baseline 3 is appropriate when the schema does the heavy lifting.

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 resource (a wallet's ranking among pump.fun operators) and enumerates exactly what the report contains: percentile, quintile, closed positions, win share, average multiple, loss share, quintile benchmarks. It is clear what the tool produces, but it never distinguishes itself from the sibling botsharper_check_wallet, which an agent could easily confuse with it.

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 clause 'Past facts only: no forecast, no advice' implies the boundary against predictive/advice-style siblings such as botsharper_simulate_bot, but it is an implied scope note rather than explicit when-to-use guidance. No alternative is named, and nothing says when to prefer check_wallet over this report.

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