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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the description only needs to add value beyond that. It does so by stating it uses DexScreener's public API and costs $0.01/call via x402 (USDC on base). Some behavioral traits are missing: e.g., what happens if a token isn't found, rate limiting, or response structure. But the safety/destructive profile is fully covered by annotations, and the cost/API backend is useful additional context. No contradiction.

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 extremely concise—three short sentences that front-load the core purpose and data returned, then the 'keyless' benefit, then the cost model. Every sentence serves a distinct purpose, there is no wasted text, and the information is structured for quick scanning.

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?

Given the tool's simplicity (3 parameters, no output schema, read-only), the description covers the essential use case well. It lacks details on error handling (e.g., what if a token address is invalid) or response format, but for a live price oracle with good annotations and a clear pricing model, the description is sufficiently complete for an AI agent to use it correctly. A perfect score would require mentioning response shape or fallback behavior.

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 value by clarifying the tokens parameter accepts contract addresses, tickers, or search terms, and that chainId restricts to one EVM chain. The maxConcurrency parameter's purpose is already clear from its schema description. The description does not add meaning to maxConcurrency beyond the schema, but overall it provides helpful semantic context that makes usage intuitive.

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 explicitly states the verb ('get current USD price') and resource ('any token by contract address or ticker'), along with the data returned (24h change, liquidity, volume, best DEX pair). It clearly distinguishes itself from siblings, none of which are price oracles, making its unique role obvious.

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 strong guidance: 'Keyless, no wallet, no RPC node — DexScreener's public API. Built to be called cheaply by AI agents that just need the number.' This explicitly tells the agent when to use it (when a cheap, simple price lookup is needed) and implies when not to use it (if detailed on-chain data or authentication is required). The pricing note ($0.01/call) adds further usage context. Alternatives are implicitly clear given the sibling names, which focus on jobs, listings, tenders, etc.

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