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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile, so the bar is lower. The description still adds real behavior: session defaults to the latest trading day, and tier-based ticker restrictions. It does not describe response format or pagination, but the field semantics (max_pain_expiry, max_pain_basis, wall_basis) substantially clarify what the output carries.

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?

Front-loaded with the returned fields, then usage, then defaults and tier limits, so an agent gets the essentials first. It is a dense single block rather than broken into scannable clauses, but each sentence (definitions, example, default, tier limits) carries information.

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 no output schema, the description compensates by defining each returned field and the basis/expiry qualifiers, and it covers the session default and access tiers. Nothing an agent needs to call and interpret the tool correctly is missing.

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 reinforces the 'session' default ('defaults to the latest trading day') but adds no syntax or semantics for dte_filter beyond what the schema already states. No material value added over the structured fields.

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?

States a specific verb+resource ('Dealer gamma-exposure key levels for a ticker') and enumerates exactly what it returns: gamma flip, max pain, call wall, put wall and spot. The field-level definitions (call wall = strike at/above spot with largest call gamma, etc.) let an agent distinguish it from greek_exposure without opening any schema.

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?

Gives a concrete when-to-use condition ('where price may pin, bounce, stall or accelerate') plus an example query, and states the access constraint (free/no-account: SPY and QQQ only; Pro: any ticker). It does not explicitly name sibling alternatives such as greek_exposure, so it falls short of a full when-not/alternative map.

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