get_dex_pairs

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

Since no annotations exist, the description carries full burden. It discloses that the tool returns price, volume, liquidity, and costs $0.001 USDC/query, adding transparency beyond the schema. However, it omits potential side effects, authentication needs, or rate limits. Score 3 for basic yet incomplete disclosure.

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?

Two sentences with no fluff. First sentence states purpose, second adds return data and cost. Highly concise and front-loaded. Score 5.

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?

Tool has an output schema (not shown but present), reducing need to describe return format. Description covers purpose, outputs, and cost. For a single-parameter tool, this is mostly complete. Score 4.

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?

The input schema has one required parameter 'symbol' with 0% description coverage. The description adds meaning by stating 'for a token,' implying symbol is the token symbol, but it doesn't clarify format or expectations. Given low coverage, description partially compensates. Score 3.

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 the tool retrieves DEX pair data for a token across exchanges, specifying the verb 'Get' and resource. It lacks explicit differentiation from siblings like get_quote or get_trending, but the focus on DEX pairs is distinct enough. Score 4 for clear purpose without sibling contrast.

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?

No guidance is provided on when to use this tool versus alternatives. The description mentions the cost but fails to specify context, prerequisites, or exclusions. Score 2 for minimal usage direction.

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