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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context: the 72-hour analysis window and the key/tier gating that drops the creator exchange cash-out trail for free callers. It does not cover latency, scoring methodology caveats, or error behavior.

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-loaded with the score range and subject, then the signal list and tier caveat. The pattern enumeration is dense but each item earns its place as an expectation of what the score reflects; only the phrasing is slightly compressed.

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 carries the burden of describing returns and does: a 0-100 score, the pattern breakdown, the optional cash-out trail, and what free-tier callers get. For a one-parameter read tool, nothing essential is missing.

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?

The single 'mint' parameter is fully documented in the schema (100% coverage), so the description need only align with it. It does so implicitly by referring throughout to a pump.fun token but adds no format, chain, or validation 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?

Names a specific verb and resource ('Score 0-100 ... for a pump.fun token') plus the exact analytic signals (bundled launch, creator sell-off, serial-launcher group) and time window. It is clearly distinguishable from siblings like kol_scorecard or check_token.

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?

Usage is implied — call it to assess a pump.fun mint for manipulation risk — and the tier note signals what a non-paying caller gets. But there is no explicit when-to-use, when-not-to-use, or routing to alternatives such as check_token or kol_scorecard.

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