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

With no annotations, the description carries the behavioral burden. It discloses key ranking behavior and criteria, and 'Rank' implies a read-only operation. However, it does not describe output shape, whether the tool auto-filters or merely suggests filters, or what the final 'Do not LP the meme' instruction means functionally.

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 very compact, with the core purpose front-loaded and each phrase adding selection-relevant information. No filler or redundant restatement of the tool name exists.

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?

The description is enough for basic invocation and parameter selection, but there are real gaps: no output schema means return values are unexplained, 'official' and 'meme' are undefined, and limit/minAgeHours are not addressed. For a 7-parameter tool with no annotations, this is adequate but not complete.

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%, so the description must add meaning, and it does for several parameters: quote maps to USDG/WETH, protocol/hooks map to v3/no hooks, minTvl maps to the $100k threshold, and the preferred sort theme is given. It does not explain limit or minAgeHours, and 'volume/TVL' is not an exact enum value, so it is not fully compensating.

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 states a specific verb and resource: 'Rank official stock/USDG (or stock/WETH) LP pools.' This clearly distinguishes it from generic siblings like talon_pool and gives concrete selection criteria rather than a tautology.

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 intended use case is clear: rank official stock/USDG or stock/WETH LP pools. It provides selection guidance such as preferring v3, no hooks, and a $100k TVL threshold, but does not explicitly name alternatives or define when not to use this tool versus a sibling.

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