Yahoo latest quote

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description adds context by explaining the data is derived from the chart endpoint and lists specific fields (regular market price, previous close, day range, exchange, currency). This provides useful behavioral details beyond the 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 that are direct and front-loaded with the main purpose. Every sentence adds value with no wasted words.

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?

Given the tool has one parameter, no output schema, and rich annotations, the description is fairly complete. It explains the source (chart endpoint) and data fields returned. Could mention that it returns only a single snapshot, but 'latest price snapshot' implies that limitation.

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 schema has 100% coverage with a single 'symbol' parameter described as 'Yahoo symbol, e.g. AAPL'. The description does not add additional information about the parameter beyond what the schema provides, so it meets the baseline for high coverage.

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?

Clearly states it provides a latest price snapshot for a symbol, specifying included data (regular market price, previous close, day range, exchange, currency) and distinguishes from siblings by noting it uses the chart endpoint instead of the crumb-gated quote endpoint.

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?

Indicates that this tool avoids the crumb-gated quote endpoint, implying it should be used for quick price lookups without authentication hurdles. However, it does not explicitly state when not to use it or how it compares to other related tools like yahoo_chart or yahoo_quote_summary.

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