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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the description only needs to add value beyond those. It adds auth and latency hints, but also includes irrelevant details about REST formats, commerce fields, signup, and dynamic pricing on a sibling tool (meteora_brief), which dilute the useful context.

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 overly long and padded with information unrelated to this tool (REST format options, commerce fields, x402 auth flow, signup URL, and pricing on meteora_brief). The core purpose is front-loaded, but the trailing irrelevancies reduce conciseness significantly.

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?

For a simple ranking tool with no output schema and three well-described parameters, the description covers the essential purpose, usage context, and parameter hints. However, the conflicting limit guidance could lead to suboptimal calls, keeping it from a perfect score.

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 the schema already documents the parameters. The description adds a conflicting limit recommendation ('prefer small limit (3–5)') while the schema says 'prefer 5–10', which could confuse an agent. No other parameter meaning is added beyond the schema.

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 (rank) and resource (DEX protocols) with clear sorting options (24h volume or 1d change). It also distinguishes itself from siblings by suggesting it's for macro trend discovery before deeper pool analysis.

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?

It provides clear context ('Use for macro DEX trend discovery before deeper pool analysis') but does not explicitly name alternative tools or state when not to use it. The chain filter examples and limit preference give some usage guidance.

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