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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so safety is covered; the description adds real behavioral context the schema cannot: x402 pricing ($0.03/call), the x-credit-token prepaid header for unlimited calls, a 1-free-call/day rate limit, and no API-key requirement. Some of the remaining text is promotional ('Not financial advice'), which keeps this from a 5.

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?

Front-loaded with the core purpose and the scoping parameter before any of the pricing detail, and every major clause carries information. It is somewhat sprawling with markdown-style dashes and appended pricing/disclaimer copy that could be tightened, so not a 5.

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-parameter tool with an output schema, the description covers what is needed: data coverage (every coinbase-listed stock, roster self-updating), the on-chain vs NYSE NAV caveat, and the payment/auth model. Complete enough to invoke correctly; the small redundancy around return fields is harmless.

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 there is only one parameter, so the baseline is 3. The description clarifies what omission yields (the full directory) and what the symbol returns (deepest Base pool price, aggregate liquidity, 24h move, volume), but this is mostly return-value content rather than added parameter syntax or format meaning.

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 resource and verb ('Live Base price & liquidity of Coinbase's tokenized stocks') and explicitly positions itself against the b20_safety sibling by contrast ('b20-safety says a tokenized stock is a real issuance; this says what it trades at ON-CHAIN'). An agent can distinguish this from token_price, stock_fair_value, and b20_safety without opening any schema.

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?

Gives clear conditional usage: pass symbol for one stock's deepest-pool price, omit symbol for the full directory, and notes the price can diverge from NYSE NAV. It stops short of explicit when-not-to-use or naming a competing price sibling (e.g. token_price / multi_price), so it is clear context rather than full routing guidance.

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