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

Discloses caching behavior (10 minutes, refreshed on-demand) and data source (GeckoTerminal). No annotations present, but description does not mention error handling or rate limits, which would be helpful.

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, each providing distinct value (API mapping, returned data, caching, parameter source). Front-loaded with key action. No fluff.

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 the simple tool (1 param, no output schema), the description covers all necessary aspects: what it returns, caching, parameter source. No gaps evident.

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% with a clear description. The tool description adds extra context by linking the id to search_liquidity_pools and emphasizing it's numeric.

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 real-time momentum data for a specific pool, listing specific metrics (volume, price changes, etc.). It distinguishes from sibling search_liquidity_pools by explicitly mentioning to use its id field.

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?

Provides clear usage context: use when you have a pool id from search_liquidity_pools. Does not explicitly state when not to use, but the guidance is sufficient.

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