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

With empty annotations, the description carries the full burden of behavioral disclosure. It adds 'live' and 'DEX' context beyond the tool name, but it does not explain quote semantics, freshness, failure modes, or any constraints on the data.

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 a single front-loaded sentence with no filler; the parenthetical adds essential asset-class context. It is appropriately sized for a one-line tool summary.

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 tool with no output schema, no annotations, and zero schema description coverage, this is insufficient for correct invocation. The required query parameter's format is unstated, and no guidance is given for typical queries.

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 0%, and the description adds no parameter-level meaning. An agent cannot tell whether query expects a ticker, contract address, or Base token name, nor what limit controls.

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 identifies the tool's output as live DEX quotes and scopes the resource to tokenized equities, specifically Coinbase B20 stock tokens on Base. This distinguishes it from generic crypto price tools and orderbook tools in the sibling list, though it lacks an explicit verb.

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 intended use is implied: call this tool when the agent needs live DEX quotes for tokenized equities. However, there are no explicit when/when-not conditions and no sibling alternatives are named, so routing is left largely to inference.

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