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

Goes well beyond the readOnlyHint annotation by disclosing that signed output depends on an explicit dealer-positioning scenario and that the numbers are modeled, not observed orders. It also explains what the what-if path actually does (reprices the same frozen contracts, drops expired contracts via horizon_hours), which is exactly the kind of caveat an agent needs before trusting the output.

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?

Purpose is front-loaded, but the body is one very dense run-on sentence cramming output enumeration, what-if mechanics, and disclaimers together. Much of the output listing duplicates what a reader would infer from parameter names, and the dense packing makes skimming harder than a short bulleted structure would.

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 and 8 parameters, the description carries the return-value burden and does enumerate the output blocks (GEX, walls, flips, regime, funding/OI block), so an agent knows what comes back. Remaining gaps are minor: no indication of result size, timing, or freshness for a computation this heavy.

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 coverage is 100%, so the baseline is 3; the description additionally clarifies parameter interactions not obvious from the schema, such as any what-if parameter implying hedging and horizon_hours dropping contracts that expire in the interval. It still leaves details like price_change_pct's relationship to the built-in ±0.5–5% ladder slightly ambiguous.

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 resource and computation: crypto options gamma exposure (gross and dealer-signed GEX) by strike/expiry, plus walls, flip levels, and a rule-based options regime. This clearly separates it from siblings like options_chain (raw chain) or options_volatility, though it never names those siblings explicitly.

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?

Usage is implied through the what-if and hedging mechanics ('hedging=true adds theoretical dealer hedge ladders', 'target_price / horizon_hours / iv_change reprice the same frozen contracts'), but there is no statement of when to reach for this tool versus options_positioning, options_volatility, or flow_levels, and no exclusions.

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