csf_disable

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

With no annotations, the description carries the safety burden, and it does so well: it warns 'Dangerous', states 'the host is unprotected until re-enabled', and discloses the environment-variable gate. It also names the exact operation 'csf -x'. It does not describe response behavior or confirm semantics, but for a single-action firewall toggle the most important behavioral traits are 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?

Four short, high-density sentences. Every line earns its place: the operation, the danger, the gate, the alternative, and the argument note. No filler, no redundant restatement of the schema, and the risk warning is 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?

For a one-argument dangerous tool with no annotations and an output schema, the description is largely complete: it explains the main side effect, the guard condition, and the preferred alternative. The only real gap is the exact confirm value needed to execute (true vs false), which is partly covered by 'confirm: Required' but would benefit from being explicit.

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 coverage is 0% and the only parameter, confirm, has no description and default false. The description says 'confirm: Required', which tells the agent it must be provided, but it does not explicitly say it must be set to true or describe consequence of leaving the default. This is minimal but usable guidance for a self-explanatory boolean-like parameter; however the line also conflicts with the schema's 'Required parameters: 0' and default false, creating ambiguity.

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 states a clear verb and resource: 'Disable CSF (csf -x)'. It immediately flags the dangerous, host-wide effect, and includes an explicit alternative, 'Prefer csf_unblock_ip instead', which distinguishes it from the closely related sibling tool. This gives an agent a precise mental model of what the tool does and what it is not for.

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?

The description gives explicit routing guidance: 'Prefer csf_unblock_ip instead' tells the agent not to use this for unblocking a single IP. It also states an operational gate, 'Blocked unless ENABLE_CSF_DISABLE=true', so the agent knows when the call will be permitted. It does not fully spell out the converse case (e.g., 'use csf_enable to re-enable'), but the warning 'until re-enabled' implies it.

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