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

Annotations only say read-only and open-world; the description goes much further by naming the ordering guarantee (newest first), the specific red-flag heuristics triggered (no liquidity, sells far below buys, extreme FDV/liquidity), and a real cost gate ($0.005 USDC per call via x402 with a URL). Cost and payment-gating disclosure is exactly the kind of behavior annotations cannot convey.

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?

One dense paragraph, front-loaded with the resource and ordering, then filters, then the follow-on action, then pricing. Every clause carries information; nothing is repeated or padded.

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?

There is no output schema, and the description compensates by enumerating the returned fields (age in minutes, liquidity, 5m/1h volume, buy/sell split, red flags). Combined with pricing and the recommended next call, an agent has everything needed to invoke it and interpret results.

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%, so all four parameters are already documented with defaults and ranges. The description only restates the liquidity/age filters in prose and adds nothing about the chain or payment parameter, so the 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 specific resource ('Freshest DEX pools on Solana or Base, newest first') plus the exact fields returned (age, liquidity, 5m/1h volume, buys/sells, red flags). That is enough to separate it from sibling feeds like token_pairs, token_new_profiles, or token_boosted without opening a schema.

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?

Gives concrete operating instructions ('filter by minimum liquidity and maximum age') and a follow-on step ('pipe results into token-sell-check before buying'), naming a sibling explicitly. It never states when NOT to use it versus a broader pool feed like token_pairs, so it falls short of full when/when-not guidance.

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