get_option_quote

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

No annotations are provided, so the description must convey behavior. It states the tool retrieves snapshot/Greeks, implying read-only, but does not explicitly confirm read-only nature, mention rate limits, authentication needs, or data freshness. It adds the legs format but lacks deeper behavioral context.

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 concise, using two sentences to convey purpose, parameter format, and exclusion. It is front-loaded with the main action and efficiently covers key points without extraneous content.

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 has one complex parameter and no output schema or annotations. The description adequately explains the input format and usage boundaries, but it does not describe the return structure or constraints on legs (e.g., max quantity). Given the complexity, more detail on output would improve completeness.

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 input schema for 'legs' is minimal (array of objects with additionalProperties true) and has 0% description coverage. The description compensates by specifying the exact structure: {code, action: BUY|SELL, quantity}, providing crucial meaning beyond the schema.

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: 'Get option snapshot/Greeks for one or more legs.' It specifies the resource (option snapshot/Greeks) and the action (Get), and distinguishes from the sibling tool 'get_option_strategy_analysis' for combo bid/ask. The Chinese translation reinforces 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?

The description explicitly states when NOT to use this tool ('NOT for combo bid/ask') and provides an alternative ('use get_option_strategy_analysis'), offering clear usage guidance. This helps an AI agent avoid misapplication.

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