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

No annotations exist, so the description carries the full burden, and it does disclose the behavioral core: the tool detects regime changes and reports a transition probability rather than just a static label. However, it says nothing about update frequency, lookback window, latency, or whether the result is cached — all relevant for a real-time regime detector whose output an agent may act on.

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?

A single compact sentence that front-loads the cost and then the purpose, with the regime vocabulary embedded so the agent learns the output domain immediately. No filler or redundancy.

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?

With only one optional parameter, no output schema, and no annotations, the definition is nearly complete — it tells the agent what regime labels and probability come back. The gaps are the missing timing semantics (how fresh or frequent the detection is) and any indication of how to interpret 'transition probability'.

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?

Schema description coverage is 100% for the single optional 'coin' enum parameter, so the schema already documents the allowed symbols and the BTC default. The description adds no meaning beyond that, which is acceptable given full coverage — baseline 3.

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?

Names a specific resource and action: a 'crypto market regime transition detector' that 'flags active shifts between TRENDING, RANGING, CRISIS, and RECOVERY volatility regimes.' The enumerated regime labels make the output concept concrete. It stops short of distinguishing itself from the siblings 'regime' and 'regime_transition_probability', which sound closely related.

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 when-to-use guidance at all — nothing says when to pick this over 'regime' (presumably current state) or 'regime_transition_probability' (presumably the probability component alone). The only implicit signal is the word 'active shifts', which hints at transition detection but leaves the agent to infer the routing rule.

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