signallord_get_regime

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

The description adds significant value beyond annotations by detailing output tiers (free vs premium), the six regimes, and the 20+ features used. Annotations indicate readOnly and idempotent, which are consistent with the described behavior.

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 well-structured with bullet points and front-loaded with the primary purpose. While somewhat verbose, every sentence adds valuable information, and the format aids readability.

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 complex tool with many outputs, the description covers regime types, similar historical periods, outcome probabilities, and tier differences. The output schema exists, so return format documentation is not required.

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 coverage is 0% but the only parameter (response_format) is optional with a default and is trivial. The description does not mention it, which is acceptable given its simplicity.

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 the current Bitcoin market regime with historical context and outcome probabilities, listing six regimes and the data sources. It distinguishes from siblings like signallord_get_regime_history by positioning itself as the flagship intelligence tool.

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 it's the primary regime detection tool but does not explicitly state when to use it versus alternatives or when not to use it. It mentions high-value signals but lacks direct usage guidance.

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