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

Goes well past the annotations by disclosing the exact auth mechanics (Bearer claim from pumppill.org/premium, or one x402 USDC-on-Base payment per call), the semantics of the attention filter, and that narrative/trend columns are deliberately withheld. This is the kind of context annotations cannot carry.

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-loads the resource and contents, then layers access and filter caveats. Dense but every clause carries information; no filler sentences.

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, the description still sketches the row contents (market cap at logging, move since) and explicitly names withheld columns, plus the access model. The remaining gap is the unexplained hours/limit parameters.

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 0% and neither of the two parameters (hours, limit) is explained in the description. The defaults (24, 25) are inferable only from the schema, but the meaning and interaction of the time window and result cap are left undocumented.

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 (the premium call table), the exact contents (Solana tokens PumpPill logged for members, newest first, with market cap at logging and move since), and the audience. It is clearly distinguishable from siblings like sol_token_detail or rh_flagged_recent.

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?

Implies usage via the 'MEMBERS' framing and the paywall, but never states when to reach for this over outcomes_measured, exit_check, or the rh_*/sol_* scanners. The access condition is given; the selection condition against alternatives is not.

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