Crypto market regime classifier

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

No annotations provided, so the description carries full burden. It mentions the tool is powered by a live production bot and returns a verdict, but does not disclose read-only behavior, rate limits, or potential side effects. Missing explicit assurance of non-destructiveness.

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 two sentences, front-loaded with the primary purpose, and contains no fluff. Every sentence contributes value, including usage guidance and output description.

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 classifier with one parameter and no output schema, the description explains the output format (regime + verdict) and supported assets. It could elaborate on how the suitability verdict is determined, but overall it is sufficient.

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 fully documents the single 'asset' parameter with an enum and description (100% coverage). The description adds no additional parameter-specific details beyond what the schema already provides, so baseline 3 is appropriate.

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's function: classifying market regime (chop/trend_up/trend_down/high_vol) for major crypto pairs, and returning a grid_suitability verdict. This distinguishes it from siblings like crypto_sentiment (sentiment analysis) and pricecheck (price data).

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 explicitly advises use before deploying grid bots, mean-reversion, or trend-follow strategies on a specific set of assets (SOL, XLM, etc.). It does not mention when to avoid or compare to sibling tools like crypto_sentiment, but the context is clear.

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