get_kill_switch

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

Discloses read-only nature, the idle behavior when no engine has written a snapshot, and the return fields. No annotations provided, so description fully covers behavioral traits without contradiction.

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 succinct sentences: first defines purpose and return, second gives common queries, third adds edge case and read-only note. No unnecessary words, front-loaded.

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?

Given single optional parameter, no output schema, and no annotations, the description covers purpose, usage, behavior, and edge case completely. Lists return fields sufficiently.

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 only parameter (state_path) is fully described in the schema (100% coverage). The description adds no extra semantics beyond what the schema already provides, earning a baseline of 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?

Clearly states the action ('Read kill-switch state'), the resource ('from the runtime state snapshot'), and the return structure. Explicitly distinguishes from the sibling tool set_kill_switch.

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?

Provides explicit use cases ('is trading halted' / 'why was the kill switch tripped') and explains the idle response scenario when no snapshot exists. Clearly indicates it is read-only and directs the user to set_kill_switch for flipping.

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