Real best Solana DEX pools (wash-filtered)

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

With no annotations provided, the description carries the full burden. It discloses that the tool filters out wash-traded and fake-volume pools, ranks by risk-adjusted fee yield, and returns an excluded list explaining dropped pools. It also mentions it's paid ($0.05). This provides key behavioral traits without contradictions.

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?

The description is three sentences with no fluff. The first sentence states the main purpose, the second details the output, and the third notes the cost. It is front-loaded and efficient.

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?

Given no output schema, the description explains what is returned (clean pools and excluded list) and which DEXes are covered. It is fairly complete for a tool with 2 parameters, though it could be more explicit about the output format.

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 100%, so the baseline is 3. The description does not add parameter-specific meaning beyond what the schema already describes (limit and minTvlUsd with defaults). It adds context about the overall output (excluded list) but not parameter details.

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?

The description clearly states it returns the best Solana DEX pools with wash-trading and fake-volume filtered out, ranked by risk-adjusted fee yield. It specifies the specific verb 'returns' and the resource 'best Solana DEX pools', distinguishing it from sibling tools like 'analyze_pools' which likely analyze pools rather than return a ranked list.

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 description implies usage context (for decision-ready pools from top DEXes) but does not explicitly state when to use this tool versus alternatives like 'analyze_pools' or when not to use it. No exclusions or alternative recommendations are provided.

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