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

Annotations already declare read-only, idempotent, open-world, non-destructive. The description adds real behavioral context beyond them: ~10s recompute cadence during market hours, the funded-API-key requirement, and a degraded fallback (delayed headline preview with regime/spot/walls/gamma flip/net GEX only) when unauthenticated.

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-loads the key value proposition, but the first two sentences restate the same field list ('walls, gamma flip, net GEX, regime') redundantly, and the long enumeration of outputs is not tightly organized. It is informative but bloated.

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 carries the burden of describing returns, and it does so thoroughly: pressure-point strike ladder, 50%/80% bands, VIX term structure, 0DTE straddle move, max pain, session OHLC/gap, order flow, top-10 GEX profile, vanna/charm totals. The auth/fallback story and the 'not investment advice' disclaimer round it out.

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?

The tool takes zero parameters, so there are no argument semantics to document; baseline is 4. Nothing in the description misleads about inputs.

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 (SPX dealer market structure) and positions it as the fullest realtime read, enumerating walls, gamma flip, net GEX, regime and strike-level detail. It reads as a superset of the sibling get_regime, but that differentiation is implied rather than stated.

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 only implied: 'the largest realtime read' and the note that a funded key is needed for the full structure suggest when to pick this over a lighter sibling like get_regime, but no explicit when/when-not or alternative-naming guidance is given.

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