dexscreenertokeninfoagent_get_specific_pair_info

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it specifies the data source ('DexScreener'), update frequency ('real-time'), and clarifies the exact nature of the pair address parameter. It doesn't mention rate limits, authentication needs, or error conditions, but provides substantial operational 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 efficiently structured with four sentences that each add value: purpose statement, data scope, source/timing, and critical parameter clarification. No wasted words, and the most important information (what the tool does and key requirements) comes first.

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 2-parameter tool with no annotations and no output schema, the description provides good coverage: it explains what data is returned ('comprehensive data... including current price, 24h volume, liquidity, price changes, and trading history'), source, and critical parameter details. It could mention response format or error handling, but covers the essentials well.

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 baseline is 3. The description adds meaningful context beyond the schema: it clarifies that 'pair_address' refers specifically to 'the LP contract address, not the quote token address' and provides examples of chain identifiers. This enhances understanding of parameter semantics significantly.

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 specific action ('Get detailed information'), resource ('specific trading pair on a decentralized exchange'), and scope ('by chain and pair address'). It distinguishes from sibling tools like 'dexscreenertokeninfoagent_search_pairs' by focusing on a specific pair rather than searching or listing.

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 description provides clear context for when to use this tool ('You must specify both the blockchain and the exact pair contract address') and clarifies what not to use ('The pair address is the LP contract address, not the quote token address'). However, it doesn't explicitly mention when to use alternatives like 'dexscreenertokeninfoagent_search_pairs' for broader searches.

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