get_ibkr_option_prices

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'snapshot' which implies a read-only operation, but doesn't clarify permissions, rate limits, data freshness, or whether this is a real-time or delayed feed. The description lacks critical behavioral context for a financial data 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?

The description is extremely concise at just 7 words, front-loading the core functionality. Every word earns its place by specifying what data is retrieved and for what instrument type, with no wasted verbiage.

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?

Given the tool's moderate complexity (4 parameters, financial data retrieval) and the presence of an output schema, the description is minimally adequate. However, with no annotations and poor parameter documentation, it leaves significant gaps in understanding the tool's behavior and proper usage.

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?

With 0% schema description coverage for all 4 parameters, the description provides minimal parameter information. It mentions 'multiple option strikes' which relates to the 'strikes' array parameter, but doesn't explain the meaning of 'symbol', 'expiry', or 'right' parameters, nor their expected formats or constraints.

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's purpose: retrieving snapshot data (bid/ask/greeks) for multiple option strikes. It specifies the verb 'snapshot' and resource 'option prices', though it doesn't explicitly differentiate from sibling tools like 'get_ibkr_snapshot' or 'get_ibkr_market_data' which might have overlapping functionality.

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 no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_ibkr_snapshot' or 'get_ibkr_market_data', nor does it specify prerequisites, exclusions, or appropriate contexts for use.

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