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

Annotations already declare readOnlyHint=true and destructiveHint=false; description adds real-time nature and data source (Finnhub) and market coverage. No contradictions. Missing info on rate limits or error behavior, but acceptable for a simple read tool.

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?

Single sentence with clear bullet-like structure. Every word earns its place—no fluff, front-loaded with purpose, then details.

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?

Tool is simple (1 param, no output schema in input but output fields described). Annotations provide safety. Covers what, where, and output fields; minor gap on error handling, but complete for typical use.

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% with detailed symbol description; description adds no extra meaning. Baseline 3 per guidelines—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?

Description states specific verb ('get real-time price quote') and resource ('stock quote'), listing exact fields (current price, change, etc.) and supported markets. Clearly distinguishes from siblings like stocks.market.candles (historical) and stocks.company.profile (info).

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 states support for US stocks, ETFs, and major global exchanges via Finnhub. Does not explicitly contrast with alternatives, but context makes it clear this is for single real-time quotes, not historical or news. Could add exclusions (e.g., not for historical).

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