yahoo_price

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's mention of 'Real-time price quote' is consistent but adds no new behavioral information beyond the real-time nature. No disclosure of rate limits or authentication needs.

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 two sentences: first states the purpose, second provides parameter details with examples. No wasted words, front-loaded with the core function.

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 tool with one parameter and no output schema, the description is adequately complete. It explains what the tool does and how to use the parameter. It could optionally mention the return value (e.g., price number), but it's not necessary given the title 'Real-Time Price Quote' and the simple interface.

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 provides only a 'symbol' string parameter without description. The description compensates by listing concrete examples (e.g., AAPL, BTC-USD, ^GSPC) and explaining the format for different asset types, which significantly adds meaning beyond the schema. Given 0% schema coverage, this is valuable.

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 it provides a 'Real-time price quote from Yahoo Finance' and lists supported asset types (stocks, crypto, ETF, index), distinguishing it from sibling tools like stock_prices or market_snapshot. The examples of symbols add specificity.

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 implies use when a single price quote is needed, but does not explicitly state when to use this tool versus alternatives like stock_prices (which may provide historical data) or market_snapshot. No guidance on when not to use or prerequisites is provided.

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