qt_get_quotes

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

With no annotations provided, the description carries the full behavioral burden. It explicitly labels the operation 'read-only', which is a key safety indicator, but it does not disclose output format, data freshness guarantees, error behavior, or any rate limits.

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?

One sentence that front-loads the core action and scope, with no filler or redundant information. Every word contributes meaning.

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?

The tool is simple, with one parameter, and the description covers purpose and input. However, with no output schema and no annotations, the return value structure and underlying data source are left undefined, leaving some ambiguity for an agent expecting quote fields.

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 description coverage is 0%, so the description must compensate. It clarifies that 'symbolIds' refers to symbol identifiers and supports 'one or more', complementing the schema's array constraints. It does not explain how to obtain or resolve symbol IDs.

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 verb ('Get'), a precise resource ('real-time quotes'), and the input scope ('one or more symbol IDs'). This clearly differentiates it from sibling tools such as qt_get_candles, qt_get_accounts, and qt_lookup_symbol.

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 'real-time' qualifier implies use for current market data as opposed to historical data from qt_get_candles, but there is no explicit statement of when to use or avoid this tool, and no alternatives are named. Usage must be inferred.

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