options_get_snapshot

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

With no annotations, the description must disclose safety and behavioral traits. It only says 'Get snapshot', implying a read, but does not describe data returned, authentication, rate limits, or whether the snapshot is real-time. This is a significant transparency gap.

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?

A single sentence is tight and readable, but it under-specifies rather than being concise. It earns a moderate score for structure.

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 lacks an output schema, and the description does not state what a snapshot contains (e.g., bid/ask, volume, Greeks). For a tool with many closely named siblings, this is incomplete.

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 provides only parameter names with no descriptions; coverage is 0%. The description does not explain the format of option_symbol (e.g., OCC symbol) or the relationship between underlying_symbol and option_symbol, so it fails to compensate.

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 uses a specific verb ('Get') and resource ('snapshot for an option contract'), clearly identifying the tool's function. However, it does not distinguish this from other snapshot/option tools beyond the name, and 'snapshot' is not defined.

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 provided on when to use this tool versus alternatives like options_get_quotes, options_get_last_trade, or reference_get_option_contract. The description gives no context for selection.

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