nemesis_set_mode

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

Discloses that 'observe' means 'learn, block nothing', 'enforce' means 'block deviations', and that enforce has a readiness gate (approved baseline) unless overridden. Consistent with destructiveHint=true and readOnlyHint=false, and adds 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?

Two sentences, front-loaded with purpose, efficient. No redundant information. Every phrase earns its place.

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 3-parameter tool with no output schema, the description covers essential usage: what the tool does, mode meanings, prerequisites, and a conditional requirement. Could mention what 'alert' does, but it's implied, and the tool is simple enough that the description is adequate.

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 covers all parameters, but the description adds semantic value by explaining the mode enum values ('observe (learn, block nothing)', 'alert', 'enforce (block deviations)') and the force parameter's effect on the enforce-readiness gate. This goes beyond the basic schema descriptions.

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's function: 'Set a Shield app's enforcement mode' with specific mode values and their effects. It distinguishes from sibling tools like nemesis_protect, nemesis_scan, etc., by focusing on enforcement mode configuration.

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 clear usage context: mode options, the requirement for an approved baseline when using 'enforce' unless force=true, and the NEMESIS_API_KEY prerequisite. Doesn't explicitly mention when not to use or alternatives, but offers enough context for correct invocation.

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