stock_snapshot_quote

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

With no annotations, the description carries the full burden. It discloses the core behavior: returns the real-time last BBO/NBBO quote. However, it does not mention any side effects, limitations, data delays, or prerequisites, which is a gap for a simple read operation. It is not misleading, but it is not deeply transparent.

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 a single, short sentence, making it easy to parse. However, the '[VALUE]' prefix appears to be an unfilled template placeholder, which is a minor structural defect and slightly reduces clarity.

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?

Without an output schema, the description fails to explain the return structure, multiple-symbol support (despite the schema allowing arrays), or how venue affects the response. The tool has only one required parameter but still offers optional filters (venue, min_time) that are not contextualized. Given the abundance of similar sibling tools, this description leaves significant gaps for an agent to invoke the tool correctly.

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 descriptions for all three parameters (venue, symbol, min_time) and covers 100% of the schema. The description adds no additional parameter-level details, so the baseline of 3 is appropriate.

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 identifies the tool as returning a real-time BBO/NBBO quote for a stock, which distinguishes it from sibling tools like stock_snapshot_trade or stock_snapshot_ohlc. However, it lacks an explicit verb (e.g., 'Gets') and begins with the placeholder '[VALUE]', making it a noun phrase rather than a proper action-oriented description.

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 usage for current quote retrieval (real-time last BBO/NBBO), but it does not explicitly state when to use this tool versus alternatives (e.g., historical quotes via stock_history_quote or stock_snapshot_market_value). No exclusions or alternative comparisons are provided, so the guidance is implicit rather than explicit.

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