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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely non-redundant behavior: 30-second DexScreener caching and the fact that missing values are returned as unavailable rather than fabricated. It omits that the call is paid ($0.002 / holder discount), which is a material behavior for an agent deciding whether to call.

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?

Two sentences, front-loaded with the usage trigger followed by the data payload; the field list and caching caveat both carry information. Slightly dense enumeration, but no wasted clauses.

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?

With no output schema, the description correctly compensates by enumerating the returned metrics (price, liquidity, volume/change, FDV, market cap, pool/DEX, pair age, symbol/decimals). The notable omission is the paid-call/holder-pricing model, which lives only in the title and schema rather than the description.

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% and each parameter — chain enum, token address, payment payload, holderWallet discount — is documented in the schema itself. The description adds no parameter-level detail (e.g. that only Ethereum/Base mainnet addresses are accepted) beyond what the schema already says, so the baseline 3 applies.

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 names a concrete verb+resource ('quick ERC-20 price on Ethereum or Base') and enumerates the returned fields, so an agent knows exactly what the tool produces. It does not explicitly contrast itself with nearby siblings such as token_verdict or imd_market, which is what would push this to a 5.

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?

'Use when an agent needs a quick ERC-20 price' gives a clear triggering condition scoped by chain (Ethereum or Base). There is no explicit when-not or named alternative, so the agent must infer the routing versus the verdict/research tools.

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