dexscreener_get_pairs_by_chain_and_pair

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

Annotations only include openWorldHint, which does not clarify safety or side effects. The description says 'Fetch', implying read-only, but provides no additional behavioral context such as response format, rate limits, or error behavior. With no readOnly annotation, the description carries the burden but only offers minimal insight.

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 a single, front-loaded sentence without unnecessary words. It is concise and easy to parse, though the plural 'pairs' could have been more precisely 'pair' to match the pairId parameter.

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?

With no output schema and minimal annotations, the description does not explain what the response contains, how pairId is formatted, or any limitations. Given the existence of sibling tools for searching pairs, this tool would benefit from specifying that it is for direct lookup of a specific pair, not discovery.

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 schema already explains both parameters. The description adds the claim that chainId is optional and defaults to the active wallet chain, but this directly contradicts the schema, which lists chainId as required. This misleading addition undermines the parameter semantics.

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 fetches pairs using chainId and pairId from Dexscreener. It distinguishes from sibling tools like dexscreener_search_pairs and dexscreener_get_token_pairs_by_token_address, though it does not explicitly name them. The plural 'pairs' with a singular pairId is slightly ambiguous but does not prevent understanding.

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 such as dexscreener_search_pairs. The description does not specify contexts, prerequisites, or exclusions, so the agent is left to infer usage from the name and parameter names.

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