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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses critical behavioral traits: keyless access, no wallet/RPC requirement, reliance on DexScreener's public API, and a cost of $0.01/call via x402 (USDC on base). This cost and payment mechanism are essential for an agent to know before invoking, providing significant added value.

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 and front-loaded with the core purpose, followed by key operational and cost details. Every clause serves a purpose—purpose, data fields, access requirements, and pricing—without unnecessary fluff.

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 simple price oracle with no output schema, the description covers the essential context: what data is returned, how to access it (public API, keyless), cost, and use case. It is complete for an agent to decide invocation and understand the response envelope.

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 schema already documents all parameters. The description does not add meaning beyond what is in the schema (e.g., 'contract address or ticker' is already in the tokens parameter description). It does clarify the output includes 'best DEX pair', but that is output semantics, not 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 the tool's function: 'Current USD price for any token by contract address or ticker' and lists the included data fields (24h change, liquidity, volume, best DEX pair). This is a specific verb+resource definition that distinguishes it from sibling tools like rug-pull-scorer or token-launch-radar.

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 usage context: 'Built to be called cheaply by AI agents that just need the number' implies when to use it (simple price lookups) and hints at when not to (when richer data or on-chain access is needed). It does not explicitly name alternatives, so it misses a point for exclusion guidance.

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