option_history_trade_greeks_second_order

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only adds the 'Max 1 month' constraint. It does not disclose return format, pagination behavior, calculation methodology nuances, or how 'second-order greeks' are computed. This is a significant transparency gap for a data-returning tool with no output schema.

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, with two short phrases that convey the core purpose and key constraints. It is front-loaded and wastes no words, though it is arguably too sparse given the tool's complexity.

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?

This is a complex tool with 15 parameters, no output schema, and many sibling variants. The description only mentions a date-range limit and required expiration, leaving unclear the exact nature of second-order greeks, how results are structured, and how this tool compares to first/third-order variants. It is incomplete for the tool's complexity.

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 a 'Max 1 month' constraint that applies to date parameters, which is useful context beyond the schema. However, it does not explain any parameter semantics beyond that, relying on the schema's own descriptions.

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 provides 'Second-order greeks at each trade', identifying the specific resource (trade-level second-order greeks) and operation. However, it does not explicitly differentiate from closely named siblings like option_history_greeks_second_order or option_history_trade_greeks_first_order/third_order, so it lacks strong sibling differentiation.

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 gives practical constraints: 'Max 1 month, requires expiration.' This implies when the tool is usable and what inputs are needed. However, it does not explicitly state when to prefer this over alternative greeks-history tools, nor does it provide exclusions or comparison guidance.

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