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

Annotations provide readOnlyHint=true, so the safety profile is clear. The description adds valuable behavioral context beyond annotations: DTE bucket boundaries, per-expiry granularity, and equivalence to four separate exposure calls, giving agents a concrete model of the operation.

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 three tight sentences with no wasted words. It front-loads the core definition, then provides equivalence context, then a practical use case, making it easy to scan and understand.

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?

With 100% schema coverage and a clear description of the output granularity (DTE buckets, per expiry, specific greeks), the tool is well-specified even without an output schema. The description gives agents enough to select the tool and interpret its results.

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 parameters (symbol, apiKey) are already well documented. The description adds no parameter-specific meaning, so baseline 3 is appropriate.

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 defines the tool as returning per-greek exposure aggregated by DTE buckets and per expiry, with a specific verb and resource. It distinguishes itself from sibling exposure tools by noting it is equivalent to four separate exposure calls grouped by time.

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 explicitly states the use case: 'Use to understand how GEX/DEX/VEX/CHEX rolls off across the term structure.' It implies when to choose this over individual single-greek exposure tools, though it does not explicitly name alternatives or say when not to use it.

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