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

Beyond the readOnlyHint annotation, the description adds interpretive guidance (positive skew = fear, contango slope) and explicitly disclaims predictive use. It also discloses the data source and notes the same data is available via REST. No contradictions with annotations.

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 one dense sentence that front-loads the core purpose ('Options analytics...'), then adds brief interpretive notes. Every clause contributes value without unnecessary verbosity.

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?

Given that an output schema exists, the description sufficiently explains the tool's scope by listing the metrics, the data source, and the only parameter's valid values. It gives an agent enough context to use the tool effectively.

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 input schema has 0% description coverage, but the description compensates by specifying valid values ('BTC or ETH') and clarifying that the coin is the subject of the analytics. This is adequate for a single parameter, though it doesn't specify exact string formatting (e.g., case sensitivity).

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 begins with 'Options analytics for a coin (BTC or ETH)' and enumerates specific metrics (ATM implied vol, skew, term structure, put/call OI ratio, max-pain). It clearly distinguishes itself from sibling tools by focusing on options-specific data and naming the source (Deribit).

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?

The description provides clear usage context: 'Descriptive positioning, not prediction' and labels itself as a 'DRILL-DOWN' tool. However, it does not explicitly name alternative tools or state when not to use it, relying instead on the uniqueness of options analytics among siblings.

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