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

Annotations already establish readOnly/idempotent/non-destructive safety. The description adds value beyond those with the 'latest available' staleness caveat (prices not guaranteed real-time) and the 'comparison table' output shape listing five named fields. No contradiction with annotations.

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?

Two sentences with zero waste: the first delivers function, scope, and return format; the second provides intent-mapped example queries that help an agent recognize when to call it. Everything earns its place and the key constraints are front-loaded.

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?

Strong for a 1-parameter read-only tool: the 10-symbol limit, return fields, and typical user triggers are all covered, and annotations carry the safety profile. Remaining gaps are edge behavior (handling of invalid/unknown tickaers, exact staleness window) and there is no output schema, so a more detailed return description would add value.

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 the symbols parameter is already richly documented in the schema (max 10, accepts CSV string or array, with concrete examples). The description merely repeats the 'up to 10' limit and adds no new syntax or format detail, so the baseline 3 applies.

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 ('Get'), resource ('latest available stock prices'), scope ('multiple stocks at once (up to 10)'), and return contents ('price, daily change, volume, market cap, and P/E'). The 'multiple stocks at once' phrasing and multi-stock example queries clearly distinguish it from single-quote siblings like stock_quote.

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?

Provides explicit use-case triggers with natural-language examples: 'show me FAANG stocks', 'compare tech stock prices', 'how are energy stocks doing?'. However, it doesn't explicitly name sibling alternatives (e.g., stock_quote for single-stock checks, stock_history for historical data) or state when-not-to-use it.

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