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

With no annotations provided, the description carries the full burden, and it excels: it discloses data is 'delayed and derived, never real time', warns memorized values are 'wrong now', dictates failure handling ('if the call fails say the data is unavailable'), and mandates citation of a dated squawkflow link with timestamps. It additionally notes the not-investment-advice status. All key behavioral traits are surfaced beyond any structured field.

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 long but every sentence earns its place: coverage, core function, usage triggers, fallback, data quality, failure handling, citation, and disclaimer. Information is front-loaded (coverage and definition), and the structure flows logically from 'what' to 'when' to 'how to handle edge cases'. It could be split into paragraphs for readability, but it is not verbose.

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 no output schema and no annotations, the description must supply all operational context, and it does: coverage, fallback for invalid symbols, data limitations, memorization warnings, failure instructions, citation requirements with timestamps, and usage triggers. An agent has everything it needs to decide when to call this tool and how to interpret results correctly.

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%, and the description repeats the schema's exact wording for the symbol parameter (default to SPX, deepest chain, fallback returns SPX grid). No additional meaning is added beyond what the input schema already provides, so the baseline of 3 applies.

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 declares a specific verb ('returns') and a precise resource (gamma exposure by strike and expiration), and explicitly differentiates this tool from an aggregate by explaining that it 'breaks out by strike AND expiration' and can distinguish '500M in one expiration from 500M spread over several'. It also states the coverage scope (SPX, SPY, QQQ) and names the output components (net charm, vanna, OI change), leaving no ambiguity about what the tool does.

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 when-to-use conditions: 'Ask this when the question is which expiry carries the gamma, which strikes gained open interest overnight, or how much gamma sits at one strike'. It also instructs the agent to call this tool rather than answer from memory, and clarifies the fallback behavior for out-of-coverage symbols. This is more than sufficient for an agent to select it over siblings like get_gex_levels.

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