option_history_trade_quote

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

No annotations are provided, so the description carries the burden. It discloses key behavioral traits: the time limit of 1 month, the requirement for an expiration, and the pairing of trades with quotes. This gives the agent important context about what to expect, though it could detail more about pagination or error handling, but it's adequate for a data retrieval tool.

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 sentence that conveys the core function and key constraints. It is front-loaded with the main action and avoids unnecessary words.

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 the tool has 12 parameters and no output schema, the description provides essential context: what data it returns, its scope (options), and constraints. It doesn't explain return structure, but for a history endpoint, this is often implied. The presence of many sibling tools makes the pairing aspect crucial, and it is covered.

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 covers 100% of parameters with descriptions, so baseline is 3. The description adds the 'requires expiration' reminder, which is already in the schema, and 'Max 1 month' which relates to date range parameters. No additional parameter-level meaning is provided 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 it retrieves option trade history paired with contemporaneous NBBO quotes. This distinguishes it from sibling tools like option_history_trade or option_history_quote by emphasizing the pairing. The constraints (max 1 month, requires expiration) further specify the tool's scope.

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?

It provides usage constraints ('Max 1 month', 'requires expiration') which inform when this tool can be used. However, it doesn't explicitly contrast it with alternative tools (e.g., option_history_trade for trades only), leaving some room for interpretation given the large sibling list.

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