bfm_skip_ip

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

With no annotations, the description carries the full burden, but it only says 'Add' and repeats the confirm parameter. It does not disclose side effects such as whether a currently blocked IP is also unblocked, whether the skip is persistent, or what permissions are needed.

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?

The description is short and front-loaded with the core purpose, followed by a compact Args list. It wastes no words, though the Args block could be integrated more naturally.

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 mutating firewall-related tool with zero annotations and 0% schema coverage, the description is too sparse: it lacks side effects, usage context, and any clarifications about scope or confirmation behavior. The presence of an output schema reduces the need to document return values, but not the need for operational context.

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 description coverage is 0%, so the description must compensate. It clarifies ip as 'Address to skip' and says confirm is required, but it omits IP format/range syntax and does not explain what confirm's value should be despite the schema defaulting it to false.

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 specific action ('Add an IP') and a specific resource ('the BFM skip / never-block list'), which clearly distinguishes it from siblings like bfm_unblock_ip. Even without naming alternatives, the target list is unambiguous.

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?

No guidance is given about when to choose this tool over related tools such as bfm_unblock_ip, csf_ignore_ip, or firewall_unblock_everywhere. The only usage hint is the confirm marker, which is a parameter note, not a selection criterion.

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