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

With no annotations, the description carries the full burden and does well: it discloses the pricing model, the daily free allowance, the 100-ticker cap, and the exact 402 recovery protocol (pay the returned Solana memo, re-call with the SAME args plus payment_tx). It omits data freshness/delay characteristics and behavior on invalid or partially-unresolvable tickers.

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?

Three short sentences, front-loaded with what the tool returns, then cost, then the payment-recovery path. Every sentence carries actionable information with no filler.

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 paid, batch market-data tool with an output schema already defining return values, the description covers cost, limits, auth, and error recovery well. The one meaningful gap is that it never says whether quotes are real-time or delayed, which matters for a market-data tool.

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%, so the baseline is 3, but the description adds value the schema does not: payment_tx is only valid when re-calling after a 402 with identical arguments, and agent_id scopes the free-tier counter. Those are procedural constraints rather than restatements of the field docs.

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 and resource ('Get latest quotes for many tickers in one call') and enumerates the returned fields (price, change, volume, market cap, P/E, 52-week range). The 'many tickers in one call' scope clearly separates it from the singular `quote` sibling without needing to name it.

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 concrete operating conditions: free up to 10 tickers, paid at $0.005/extra ticker above that, hard cap of 100, and a Bearer key bypass. It does not explicitly say 'use `quote` for a single symbol', so the alternative routing is implied by the batch scope rather than stated.

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