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

With no annotations, the description must carry the full burden. It does communicate that this is a read-style analytics tool and adds the useful access constraint 'Pro tier', plus the conceptual output of theta decay by session window. However, it does not disclose rate limits, authentication specifics, or anything about response shape beyond the existence of an output schema.

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 compact and front-loaded with the core purpose in the first sentence. The Pro tier note and structure enum are relevant, but the enum could have been formatted more cleanly as a list or valid-values note rather than a bare label.

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 an output schema, the description is adequate for a basic call: it names the tool's purpose, gives valid values, and notes Pro tier. It falls short on contextual completeness because it never clarifies the term 'premium compression', explains what a session window is, or differentiates this tool from adjacent analytics tools in the same suite.

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 schema description coverage is 0%, but the description compensates by enumerating the allowed structure values: iron_condor, vertical_spread_call, vertical_spread_put, single, short_call, short_put. It does not explain what each structure means or which one to choose for a given scenario, but it clearly identifies the valid inputs beyond the bare schema definition.

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 identifies the resource as a Premium Compression Heatmap and specifies the metric: theta decay velocity by session window for a multi-leg structure. It is specific enough to distinguish this from most sibling analytics tools, though it does not explicitly contrast it with any named alternative.

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 guidance on when to use this tool versus the many option-related siblings like get_gex_profile, get_skew, or get_rails. The description implies use when theta decay compression data is needed, but it provides no exclusions, prerequisites beyond 'Pro tier', or alternative routing.

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