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

There are no annotations, so the description bears the full burden of behavioral disclosure. It conveys that the output is a live gamma map with specific elements, but it does not disclose data source, update cadence, market-hours dependencies, or any caveats about the 'magnet' or 'flip' indicators. The output schema may help, but the description itself remains thin.

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 single packed sentence that front-loads the key resource and its distinguishing content elements. There is no wasted wording, and given the zero-parameter input schema, this level of brevity is appropriate.

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?

The description covers the core subject but leaves significant context gaps: it does not explain the jargon ('walls, flip, magnet, regime'), specify when the data is meaningful, or differentiate from closely related gamma tools. The presence of an output schema helps with return structure, but the lack of usage context and behavioral caveats makes this incomplete for an agent choosing among many similar market-analysis tools.

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 has zero parameters, so parameter semantics are effectively moot. The description does not need to explain inputs, and the simple factual label is sufficient for a no-argument call.

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 a specific resource ('SPY 0DTE gamma map') and lists the key content dimensions ('walls, flip, magnet, regime'), making the purpose reasonably clear. It distinguishes itself from generic tools, though it does not explicitly contrast with siblings like get_gex_profile or get_pin.

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?

No guidance is given about when to use this tool versus alternatives such as get_gex_profile, get_pin, or get_path_risk_score. The phrases 'Live SPY 0DTE' imply a real-time use case, but there is no explicit when-to-use, when-not-to-use, or alternative routing information.

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