option_snapshot_greeks_first_order

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

With no annotations available, the description carries the full burden of behavioral disclosure. It only states 'Real-time first-order greeks' and 'for all contracts on an expiration,' but does not describe read-only semantics, response structure, pagination, or potential size of results. The scope (all contracts) is useful but minimal.

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 a single, front-loaded sentence that efficiently conveys the core purpose. The '[STANDARD]' prefix adds no substantive value but does not significantly hurt. It could be slightly more informative about return scope, but remains appropriately concise.

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 12 parameters, no output schema, and no annotations, the description is under-specified. It does not explain what data is returned (e.g., timestamp, greek values, contract identifiers), how defaults behave, or how the tool relates to the broader greeks snapshot family. The high complexity demands more contextual detail.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds no additional parameter context beyond what the schema already provides; it does not highlight required parameters (symbol, expiration) or explain how filters like strike_range or min_time affect results.

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 identifies the tool as returning real-time first-order greeks (delta, gamma, theta, vega, rho) for option contracts on a given expiration. It distinguishes itself from sibling tools via the 'first-order' qualifier and the specific list of greeks, though it does not explicitly contrast with second/third-order or IV tools.

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 for when to use this tool versus alternatives. It does not mention when to prefer it over option_snapshot_greeks_all, second_order, or history variants, nor any prerequisites or context for choosing this snapshot endpoint.

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