blacklist_update

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the script path, the cron cadence it bypasses, and that entry counts are shown afterwards, but it is silent on the two-phase dry-run/apply mutation implications, host-wide side effects, and any permission requirements -- gaps the schema partly covers but the description should flag.

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?

A single sentence with the action front-loaded and only a brief parenthetical for context. Efficient and readable, though the parenthetical interrupts the main clause slightly.

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 6-parameter fleet-wide mutation tool with no annotations and no output schema, one sentence is thin. It covers what and the return summary but leaves the dry-run-then-apply workflow and mutation safety implied by the schema rather than spelled out in prose.

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 100%, so all six parameters (apply, batch, target, planHash, continueOnError, skipUnreachable) are already documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

States a specific verb and resource -- refreshing ipset blacklists -- and even names the underlying script and its normal cron trigger, which lets an agent distinguish this from ufw_rule or other firewall siblings. However it never explicitly contrasts itself against those siblings.

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 parenthetical '(normally run by /etc/cron.d/ufw-blacklist every 2 h)' implies this is a manual out-of-band refresh, which hints at when to reach for it. But there is no explicit when-to-use vs alternatives guidance and no stated prerequisites.

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