Get stock quote

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

Annotations declare readOnlyHint, so no mutation risk. The description adds valuable behavioral context: prices are delayed per the data vendor, not tick-by-tick. This goes beyond the annotations and helps the agent set user expectations.

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?

Three sentences with no redundancy: first defines output, second gives usage and alternative, third adds a caveat. Every sentence earns its place.

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 simple one-parameter tool, the description covers all essential aspects: single ticker, output fields, batch alternative, and data delay. No output schema exists, but the listed fields suffice for the agent to understand what will be returned.

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 already fully describes the 'ticker' parameter with examples (AAPL, BRK.B). The description reinforces 'ONE ticker' but adds no new parameter syntax or format details, so baseline 3 applies.

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: 'Real-time quote for ONE ticker' with specific fields (last price, change, bid/ask, high/low, volume). It explicitly differentiates from the sibling stoquant_get_quotes_batch by scope (single vs. batch).

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?

Provides explicit guidance: use for a single symbol, and for 2+ symbols use the batch tool. Also warns about data delay, setting expectations for when to use this tool.

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