signallord_get_regime_history

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the description adds value by clarifying data source (daily snapshots vs live 2-minute cycle). This provides context beyond 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?

Three sentences, each adding value. The first sentence states the core purpose, the second adds use-case context, and the third clarifies the data source. No redundant or missing words.

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 an output schema present, return values are implicitly covered. The description is complete enough for an agent to select and use this tool appropriately. A minor gap: no mention of authentication requirements, but annotations and tool context likely offset this.

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 50%: the 'days' parameter is well-described in the schema, but 'response_format' lacks description. The tool description does not add parameter-specific details. The baseline for 50% coverage expects more compensation, but the parameters are simple and the default values are clear.

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 begins with 'Get historical regime classifications' which is a specific verb and resource. It clearly distinguishes from sibling tools like signallord_get_regime (current regime) by emphasizing 'historical' and 'snapshots'.

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?

Useful for identifying regime transition patterns and duration statistics. The description notes it uses daily snapshot data rather than the live 2-minute engine cycle, implying when to prefer this over real-time tools. However, it does not explicitly name alternative tools to use or avoid.

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