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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds meaningful behavioral context: it returns all daily observations with specific data fields (bid/ask, IV, Greeks) and describes the temporal scope ('over time'). This goes beyond the annotations and clearly communicates the output nature.

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 two sentences with no wasted words. The primary purpose is front-loaded, followed by the return payload and concrete use cases. Every sentence earns its place and there is no unnecessary detail or repetition.

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?

For a simple 4-parameter tool with no output schema, the description is quite complete. It explains what the tool returns, the fields included, and provides context on why an agent would use it. It doesn't specify output format or date-sorting details, but these are not critical for a read-only historical data tool, especially with no date parameters to configure.

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 each parameter already has a clear description. The description reinforces that ticker, strike, and expiration collectively identify the contract, but it doesn't add substantial new meaning beyond the schema. The baseline of 3 applies because the schema does the heavy lifting and the description only slightly reinforces the parameter grouping.

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 tracks a specific options contract (same ticker + strike + expiration) over time and returns daily observations with evolving bid/ask, IV, and Greeks. It uses a specific verb 'track' and names the resource. It distinguishes itself from sibling tools like options_chain or options_history_chain by emphasizing single-contract behavior.

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 provides explicit use cases: 'useful for studying single-contract behavior leading up to expiration, gamma squeezes around specific strikes, etc.' This clearly indicates when to use this tool, though it doesn't explicitly name alternatives or state when not to use it. The single-contract focus implicitly differentiates it from chain-level or cross-contract tools.

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