token_price

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

The description discloses that no API key is required and that the highest-liquidity pair is auto-selected. This goes beyond the minimal schema. It does not mention error handling or rate limits, but for a simple read tool, the behavioral information is adequate.

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 concise, consisting of two sentences with no redundant information. It is front-loaded with the core action and provides necessary details efficiently.

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?

The description covers the main purpose, input, output data, and authentication. However, it does not describe the return format or potential errors (e.g., if no pair found). Given the lack of an output schema, additional context would improve completeness.

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 schema already describes the parameter 'address' as 'Token contract address'. The tool description adds 'Base token' which is slightly more specific but does not significantly enhance understanding. With 100% schema coverage, a baseline score of 3 is appropriate.

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's function: get current USD price, 24h change, liquidity, and volume for a Base token on DexScreener. It specifies the required input (contract address) and the source. However, it does not explicitly differentiate from sibling tools like 'quote' or 'market_snapshot', which may offer similar price data.

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 implies it is for Base tokens but does not mention when not to use it, nor does it reference any sibling tools. There is no context for decision-making.

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