opn_firewall_revert_now

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the existence of a pending-change timer, but it never states whether the unapplied changes are discarded, whether the revert is irreversible, or whether any privilege is required. An output schema exists, so return-value detail is not expected here.

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 economical sentence that front-loads the action and then adds the one qualifier that matters. Nothing is redundant and nothing could be trimmed without losing meaning.

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 zero-parameter action with an output schema, this is close to sufficient: the agent knows what it does and when it fires. The only real gap is that it does not situate the tool within the confirm/pending-revert workflow alongside its siblings.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no inputs are needed.

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 uses a specific verb+resource pair ("revert the pending firewall changes") plus a timing qualifier ("immediately instead of waiting for the timer"), so the action is unambiguous. It does not, however, distinguish itself from siblings like opn_config_revert or opn_firewall_confirm, which an agent may well confuse with this one.

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 phrase "instead of waiting for the timer" implies the situation in which to call it: a deferred revert is pending and you want it to happen now. There is no explicit when-not guidance and no sibling named as an alternative (e.g. confirm vs revert), leaving the agent to infer the choice.

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