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

No annotations, so the description carries the burden, and it does disclose the key trait: it is a paid call (0.05 USDC via x402). It also discloses the internal processing and the honeypot/rug filtering that reduces risk in results. It omits latency, caching and result size, which keeps this short of a 5.

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?

Three sentences: what it does, when to use it, what it costs. The pipeline is front-loaded and the price is placed where it will be seen before the call. No 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?

With no output schema and four optional parameters, the description covers the workflow, the payment requirement and the ranked-return shape. It would be stronger if it hinted what a ranked entry contains (score, token, chain) or whether the payment proof is reusable across calls, but nothing critical to correct invocation is absent.

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 75%, with chain, limit and minScore already documented in the schema, including the paymentProof 402 flow. The description adds no parameter-level detail (e.g. that minScore filters ranked output after scoring), so baseline 3 applies.

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 concrete pipeline: fetch trending tokens from GMGN, filter honeypots/rugs, run composite_signal on each, return ranked results. This distinguishes it from siblings like gmgn_trending, trending_tokens, new_token_profiles and composite_signal, which are individual steps of this composite.

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?

"Use this to discover the best current opportunities" gives a clear usage context, and naming composite_signal makes the dependency relationship visible. It does not say when to prefer the cheaper single-step siblings (gmgn_trending, trending_tokens), which is the main missing exclusion.

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