Get Quote

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses the untraded-instrument behavior with 'Untraded instruments carry traded=false', which is valuable. It does not discuss error cases or data latency, but these are less critical for a simple read-only quote tool.

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 with no filler. The key purpose is front-loaded and the behavioral note is a compact second sentence.

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 one-parameter tool with an output schema, the description covers the essential purpose, the scope (single instrument), and a non-obvious output behavior. Nothing important is missing for an agent to select and call it 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?

Schema coverage is 0%, so the description should compensate for the single `symbol` parameter. It clarifies that the tool targets one instrument but does not explain accepted symbol formats, casing, or how to find the correct symbol via search_symbols.

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?

Description states a specific action and resource: retrieving the latest quote for one instrument, and enumerates the returned fields (LTP, day range, close, YCP, change, trades, value, volume). This clearly separates it from broader market tools like market_summary or historical tools like get_price_history.

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 phrase 'Latest quote for one instrument' gives a clear condition for use: when you need a current snapshot for a single symbol. It does not explicitly list alternatives or when-not-to-use conditions, so it stops short of full routing guidance.

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