option_history_trade_greeks_first_order

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

With no annotations, the description carries the full transparency burden. It does disclose important behavioral limits (max 1 month, expiration required) and that it returns per-trade data, but it does not describe output format, error behavior, or data freshness. The disclosure is minimal but not misleading.

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 concise sentence, front-loaded with the core purpose and followed by key constraints. Every word adds value, with no redundancy or filler.

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 15 parameters, no output schema, and no annotations, yet the description only states a one-line summary and two constraints. It does not explain return structure, time range handling, or how it differs from similar tools, leaving significant gaps for such a complex endpoint.

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 schema fully documents all 15 parameters. The description adds no extra parameter semantics beyond what the schema already provides, hitting the baseline of 3.

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 indicates the tool provides first-order Greeks on a per-trade basis, and distinguishes it from related tools by noting the 1-month limit and expiration requirement. However, it lacks an explicit verb like 'Get' or 'Fetch', so it is not maximally specific.

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 useful constraints (max 1 month, requires expiration) that imply when this tool can be used, but it does not explicitly state alternatives or provide when-not-to-use guidance. Context is clear but exclusions are absent.

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