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

With annotations already declaring readOnlyHint=true, the description need not repeat safety. It adds substantive behavioral context: the tool reveals gamma flip, call/put walls, and dealer hedging support/resistance, which are not derivable from the schema or annotations. It stops short of describing pagination, API errors, or default expiration behavior, but the added domain context is valuable.

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?

Two sentences, front-loaded with the core action, no filler. Every phrase adds meaning: 'by strike' specifies scope, and the second sentence explains why the output matters for trading analysis.

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 tool with no output schema, the description gives a solid conceptual picture: gamma exposure per strike, gamma flip, walls, and support/resistance implications. It lacks explicit mention of the response shape (e.g., per-strike rows, sorting) or how expiration and min_oi affect the result, but the level of detail is sufficient for an agent to decide when to call it and what to expect conceptually.

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 all four parameters are already documented. The description adds the concept of strike-level output but does not clarify the role of min_oi, expiration, or the optional apiKey beyond the schema. It contributes marginal meaning but does not compensate for anything missing.

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 uses a specific verb-resource pair: 'Get gamma exposure (GEX) by strike' and immediately enumerates distinctive outputs (dealer gamma positioning, gamma flip, call/put walls). This clearly differentiates it from siblings like get_exposure_summary or get_historical_gex by emphasizing strike-level detail and current dealer hedging 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 communicates the tool's current-moment, strike-level GEX focus, which implies when it would be relevant (support/resistance analysis). However, it does not explicitly state when to prefer this over siblings such as get_historical_gex, get_exposure_summary, or get_dealer_premium, nor does it mention any exclusions or caveats.

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