set_killswitch

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

With no annotations, the description fully explains the core effect (blocks traffic) and the return value. Does not cover potential side effects like persistence or permissions, but the key behavioral trait is disclosed.

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 plus structured Args/Returns. Front-loaded with purpose, then logical explanation, and specific parameter info. Every sentence adds value with no 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?

For a simple toggle tool, the description covers the effect, parameter, and return. Could mention prerequisites (e.g., VPN connection state) or idempotency, but the presence of an output schema reduces the need for full return specification.

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 description explicitly explains the single parameter 'enabled' with True/False mapping, compensating for the schema's 0% coverage. Adds meaning beyond the schema's type-only specification.

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 verb 'Enable or disable' and the specific resource 'kill switch (lockdown mode)'. Unique among siblings, leaving no ambiguity about its function.

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 context by explaining the effect of enabling (blocks all traffic unless VPN connected) but lacks explicit guidance on when to use versus alternatives like connect/disconnect or set_daita. No exclusions or prerequisites mentioned.

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