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

Beyond the annotations (read-only, idempotent, open-world), the description discloses pricing ($0.01 per call over x402 on Base), auth needs (x-credit-token header for unlimited calls or free daily call), and that no wallet or API key is required. It also names DexScreener as the data source, adding meaningful 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 front-loaded with the core resource and purpose, then adds valuable operational details about pricing, auth, and use case. There is slight redundancy between the opening phrase and the later metadata list, but no irrelevant content.

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 single-required-parameter tool with full schema coverage and an output schema, the description is complete: it covers intended use, data source, required input, pricing, authentication, and access constraints. No major operational information is missing.

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% and the schema already defines 'address' as a token contract address. The description only repeats that address is required and implies it is a Base token address, adding no meaningful format, validation, or additional semantic detail beyond the schema.

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 function: return name, symbol, logo image, website, social links, price, and liquidity for a Base token via DexScreener. It uses a specific verb-plus-resource structure and differentiates itself from price/risk-focused siblings by emphasizing metadata and social enrichment.

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 states a clear context ('For agents and UIs enriching a token') and identifies the required input (address). It does not explicitly name when-not-to-use or alternatives, but the intended use case is evident enough for an agent to select it appropriately.

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