yahoo_price

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

With no annotations, the description must convey safety and behavior. It states 'real-time price quote,' implying a read-only fetch, which covers the basic safety profile. However, it doesn't disclose potential limitations such as delayed data, symbol validation errors, or whether additional fields (bid/ask, volume) are returned.

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 one-sentence summary front-loads the purpose, followed by a well-organized list of symbol examples. Every line adds value, and the structure is easy to scan.

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 single-parameter price quote tool with no output schema, the description covers the essential usage: which symbols are accepted and what the tool returns (a real-time price). It lacks explicit detail on output format or error behavior, but given the simplicity, it is nearly complete.

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?

The input schema only provides 'symbol' with no description. The description compensates with a detailed 'Args:' section containing symbol formats and examples for stocks, crypto, ETFs, indices, FX, and Turkish securities, providing essential semantics 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 opens with 'Real-time price quote from Yahoo Finance for any stock, crypto, ETF or index,' clearly stating the verb (get price quote), resource (Yahoo Finance), and scope. This distinguishes it from sibling tools like scanners and analysis tools.

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 gives extensive examples of valid symbols across asset classes, establishing clear context for when to use this tool (whenever a single real-time price is needed). It does not explicitly name alternative tools or exclusions, but the asset-class coverage implicitly defines its scope.

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