get_ibkr_snapshot

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. While 'Snapshot' implies a read operation, it doesn't specify whether this requires authentication, has rate limits, provides real-time vs delayed data, or what happens with invalid symbols. The description lacks essential 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 5 words, with no wasted language. It's front-loaded with the core functionality and uses efficient phrasing. Every word earns its place in this minimal description.

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 existence of an output schema (which presumably documents return values), the description doesn't need to explain return format. However, for a financial data tool with 4 parameters and no annotations, the description is too minimal. It doesn't address authentication needs, data freshness, error conditions, or parameter semantics that would help an agent use 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?

With 0% schema description coverage and 4 parameters (1 required, 3 with defaults), the description provides no information about any parameters. It doesn't explain what 'symbol' represents, what 'sec_type' options exist beyond the default 'STK', or how 'exchange' and 'currency' affect the snapshot. The description fails to compensate for the complete lack of schema documentation.

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 action ('Snapshot') and resource ('latest price for any security'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate this from sibling tools like 'get_ibkr_market_data' or 'get_ibkr_option_prices', which likely provide similar financial data.

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. With multiple sibling tools related to market data and pricing, there's no indication of when this specific snapshot tool is appropriate versus other data retrieval tools.

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