Cboe delayed quote (stocks / indices)

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds useful behavioral context: the quote is delayed by ~15 minutes, returns specific fields, and requires no API key. This adds value beyond annotations, though it does not address rate limits or potential errors.

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 front-loaded with the core purpose and returns data, followed by a concise explanation of symbol format with examples. Every sentence serves a purpose; there is no redundancy or unnecessary detail.

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 quote tool with one parameter, no output schema, and annotations covering safety, the description is fully adequate. It explains the delay, return fields, and symbol rules, and distinguishes the data source. No gaps are apparent.

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?

Schema coverage is 100% with a description for the 'symbol' parameter. The description enriches this by explaining the underscore prefix rule for indices and providing concrete examples (AAPL, _SPX), which clarify usage beyond the schema's brief description.

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 returns a delayed quote snapshot for equities, ETFs, or indices from Cboe, specifying the data fields (last, bid/ask, OHLC, volume, metadata). It distinguishes itself from sibling tools like yahoo_quote by noting independence from Yahoo, and the title differentiates it from other Cboe tools (cboe_history, cboe_options_chain).

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 provides explicit guidance on symbol format (tickers as-is, indices with underscore prefix) and gives examples. It implies it's an alternative to Yahoo by saying 'independent of Yahoo,' but does not explicitly state when to use this tool versus other Cboe tools or Yahoo. The context is clear but lacks explicit exclusion criteria.

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