Get stock quote

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

The description adds meaningful behavioral context beyond the annotations: price delay up to ~15 minutes, non-official prices, and independent symbol lookup behavior. These details help the agent understand reliability and failure modes, which annotations do not convey.

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?

Every sentence serves a distinct purpose: core function, symbol format, usage alternatives, and limitations. The description is front-loaded with the primary purpose and is appropriately sized for the tool's complexity.

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?

Despite no output schema, the description completely covers what the tool returns, how to format inputs, how to use alternatives, and important caveats. It also handles multi-symbol behavior, making it self-sufficient for correct invocation.

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 parameter description includes basic examples. The tool description enriches this with Yahoo-style symbol formats (e.g., international suffixes like RELIANCE.NS, 7203.T) and edge-case behavior (one bad symbol does not fail the rest), adding value beyond the schema.

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 returns 'Latest price and daily change for one or more stocks, ETFs, or indices, from Yahoo Finance.' This is a specific verb+resource+scope definition and distinguishes from siblings by explicitly referencing get_price_history and get_crypto_price for other use cases.

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?

The description provides explicit guidance on when to use this tool vs alternatives: 'Call search_symbols first if you only have a company name' and 'use get_price_history for a series or a period return, and get_crypto_price for cryptocurrencies.' This is clear and actionable.

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