detect_market_regime

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

Annotations already indicate idempotent and non-destructive behavior. The description adds 'returns classification, strategies, risk multiplier' but lacks deeper behavioral context (e.g., external API calls, latency, required data freshness). No contradiction 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?

Two clear sentences: first states purpose and inputs, second states outputs. No extraneous text, front-loaded with key information.

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?

Returns are partially described (regime, strategies, risk multiplier) but no output schema exists. Missing details on error handling, data timeframe, or input constraints. Given 8 undocumented parameters, completeness is adequate but not thorough.

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 has 8 parameters with 0% description coverage in schema. The description only groups inputs as 'VIX, SPY trend, breadth, credit signals', failing to explain individual parameters like 'spy_price', 'put_call_ratio', etc. This is insufficient given the lack of schema descriptions.

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 detects market regime from specific inputs (VIX, SPY trend, breadth, credit signals) and lists outputs (classification, strategies, risk multiplier). It distinguishes from sibling tools like 'get_current_regime' (cached) and 'detect_regime_hmm' (different method).

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 implies usage for regime detection with live data but does not explicitly contrast with siblings like 'get_current_regime' or 'detect_regime_hmm'. No when-to-use or when-not-to-use guidance is provided.

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