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

Annotations already declare read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds useful context about external source dependencies (Tradier/Polygon, SEC FTD, SqueezeOS oracle), but omits rate limits, latency, failure modes, or what 'classify' actually entails.

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?

It is a single sentence with no filler, but it is a dense noun phrase that front-loads data sources rather than the tool's action. The structure could be improved by leading with what the tool does.

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 classification tool with no output schema, the description fails to explain the output categories, thresholds, or how the GEX and FTD data combine into a regime. An agent cannot know what a successful response looks like or how to interpret it.

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% for the single ticker parameter, so the schema already documents it fully. The description adds no additional meaning about the ticker parameter or any formatting expectations. Baseline 3 is appropriate when the schema does all the work.

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 names specific data sources and metrics (dealer GEX from Tradier/Polygon, Reg SHO threshold status from SEC/SqueezeOS), but it never states the action of classifying a microstructure regime or what the classification output represents. It also fails to distinguish itself from sibling track_gamma_squeeze_mechanics, which also concerns gamma exposure.

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?

There is no indication of when to use this tool versus alternatives, no prerequisites, no exclusions, and no explanation of how the two data sources should factor into a decision. The description is purely descriptive of underlying data.

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