Crypto volatility / drawdown risk regime

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

No annotations are provided, so the description carries full burden. It explains the output (low/med/high regime), the basis (volatility vs 30-day baseline), and the applicability to major crypto assets. It adds context about the underlying classifier and the tool's non-destructive nature. Some limitations or edge cases could be added, but overall it provides good behavioral insight.

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 three sentences, concisely front-loading purpose, use case, and supported assets. No extraneous information; every sentence earns its place.

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 simple tool with one parameter and no output schema, the description explains the return value (low/med/high regime), the logic (volatility vs baseline), the supported assets, and a use case. It references the sibling tool for context, making it complete for an agent to decide whether to invoke 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?

The schema description coverage is 100%—the single 'asset' parameter is fully described with an enum. The description merely restates the supported assets ('One of SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA'), adding no meaning beyond the schema. Baseline 3 is appropriate since the schema already handles semantics.

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 returns a volatility/drawdown risk regime (low/med/high) for a major crypto asset, specifically comparing current volatility to a 30-day baseline. It distinguishes itself from the sibling crypto_regime tool by noting it extends the same classifier but focuses on volatility risk. The verb 'tells' and resource 'risk regime' are specific.

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 context by stating the tool is 'useful for position sizing and stop-placement logic' and that it extends the classifier behind crypto_regime. This gives implicit guidance on when to use it vs. the sibling tool. However, it does not explicitly state when not to use it or provide exclusionary criteria.

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