get_quotes

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

With no annotations, the description discloses key behaviors: each symbol is looked up individually, unsuccessful symbols appear under 'not_found' instead of failing the whole call, and it lists the exact fields returned (currency, last price, previous close, open, day high/low, market cap). This adds substantial transparency beyond a simple 'get quotes' statement.

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?

The description is compact and well-structured: first sentence states purpose, second paragraph explains usage and output behavior, third sets constraints. Every sentence earns its place with no redundancy.

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?

The tool is simple (one parameter), has an output schema, and the description covers purpose, usage, error handling, and parameter constraints. It fully equips an agent to select and invoke the tool correctly without additional context.

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%, so baseline is 3. The description reinforces the symbol format constraint and adds context about multi-symbol comparison and not_found behavior, which adds value beyond the schema's parameter description.

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?

The description clearly states the tool's function: fetching compact current quotes for multiple Yahoo symbols in one call. The verb 'get' plus resource 'quotes' and plural 'several' distinguishes it from singular get_quote, making the purpose unambiguous.

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?

It explicitly says 'Use this to compare or fetch prices for multiple tickers at once', providing a clear use case. It also sets constraints (native tickers only, not ISINs/WKNs/names), guiding proper usage. It does not explicitly name alternatives, but the sibling list provides context.

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