set_kill_switch

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

Describes immediate effect of active and dry_run, but lacks details on permanence, permissions, or side effects for a potentially destructive action. No annotations to compensate.

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 sentences, front-loaded with purpose and key behaviors. Every sentence adds distinct value without 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?

Covers main behaviors and dry_run nuance. Missing output schema info and explicit mention of mutation, but adequate for a simple toggle tool.

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?

Adds meaningful context for active and dry_run beyond schema. Only reason parameter is described in schema; description clarifies defaults and usage.

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?

Describes setting the kill-switch state with clear verb-resource pairing. Distinguished from sibling get_kill_switch by implication, but not explicitly mentioned.

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?

States explicit use cases: emergency halt and resume after manual review. Dry-run behavior documented for safe usage, though no alternatives listed.

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