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

With no annotations, the description carries the full burden and does well: it discloses the payment mechanism, authentication options, the educational/non-advice nature, and the limitation that raw exposures are not provided. It does not cover rate limits or error behavior, but the core behavioral traits are clearly stated.

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 a dense block of text with pricing, payment, auth, and catalog guidance mixed together. It is front-loaded with the core purpose, but the 'HOW TO PAY' section and catalog pointer add length. It is informative but not concise.

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 one-parameter tool with no output schema, the description covers the main output fields, the tool's limitations, and the access/payment model. It does not detail the exact JSON response structure, but the named outputs and constraints make it reasonably complete for an agent to invoke 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 coverage is 0%, so the description must compensate. It adds meaning by specifying the parameter is an equity/ETF symbol, but it does not clarify format, case sensitivity, or examples. For a single simple parameter this is adequate but not rich.

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 clearly states the tool provides dealer-regime classification for one equity/ETF symbol, including specific output labels (positive_gamma_pinning, negative_gamma_amplifying) and gamma_bias. This is a specific verb+resource+scope that distinguishes it from sibling tools like get_market_regime or get_volatility_scan.

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?

It gives context for use ('for squeeze and volatility analysis') and notes that raw gamma dollar exposures are not redistributed, implying this tool is for regime classification rather than raw data. However, it does not explicitly name alternatives or state when not to use this tool versus siblings.

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