ibkr_get_quote

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

With no annotations provided, the description alone must disclose behavioral traits. It states 'Get a market data snapshot' implying a read operation, but does not mention latency, rate limits, authentication requirements, error behavior, or what constitutes a snapshot. The lack of detail leaves significant ambiguity.

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 brief with two sentences, both adding value: the first defines the core action, the second provides critical option parameter guidance. No unnecessary words. However, it could be more informative without sacrificing conciseness.

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 should explain return values. It does not describe what the snapshot includes (e.g., bid, ask, last price). Also lacks prerequisites, error handling, or usage context for a 7-parameter tool. The description is too sparse for the complexity.

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 has 0% description coverage, so the description must compensate for all 7 parameters. It only addresses three option-related parameters (expiry, strike, right) with format hints, but ignores symbol, sec_type, exchange, and currency. This is insufficient to fully clarify parameter meanings.

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 states 'Get a market data snapshot', which clearly indicates the tool retrieves current market data. The addition of option parameter requirements provides specificity. However, it does not explicitly differentiate from sibling tools like ibkr_get_historical_bars or ibkr_get_option_chain, but the snapshot nature implies a distinct purpose.

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?

No guidance is given on when to use this tool versus alternatives, such as ibkr_get_historical_bars for historical data or ibkr_get_option_chain for option chains. The description merely notes option parameters but lacks context on tool selection or exclusions.

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