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

Goes well beyond the readOnly/openWorld annotations: discloses the $0.002 x402 USDC-on-Base charge, that failures (unknown symbol, bad input, RPC down) are not charged on Base but may be charged on other rails, and that returned content is untrusted third-party data. It also links buyer terms, which matters for a paid 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?

Tight, front-loaded sentences that pack scope, format, return fields, and error/payment behavior without filler. The legal/terms clause is necessarily dense but slightly bloats the tail of a one-line description.

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 partially compensates by naming the returned fields (paused flags, supply, supply cap, multiplier, issuer, token address) and covering failure behavior and payment. What it lacks is any indication of response shape, such as a per-token vs aggregate object, or caching/freshness.

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 already documents accepted forms (AAPL, AAPLc, token address, omit for all), so the description's near-identical wording adds little. The only net-new detail is the count of 12 listed stocks; otherwise the schema does the heavy lifting.

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?

States a specific verb+resource (tokenized stock status for Coinbase tokenized stocks on Base) and enumerates concrete tickers (AAPLc, NVDAc, TSLAc). It also draws the boundary against price-oriented siblings with 'On-chain token state only, no price,' so an agent can distinguish it from market_quote or token_meta.

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?

Explicitly gives the call pattern: optional symbol, omit for all 12, and states what is out of scope (no price). It stops short of naming a concrete alternative tool for pricing, so the exclusion is implied rather than routed.

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