pve_revert_node_network

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

No annotations are provided, so the description carries the full burden. 'Revert' implies a destructive operation that undoes changes, but the description doesn't specify whether this requires special permissions, if it's irreversible, what happens to the node during the revert, or if there are rate limits. This leaves critical behavioral aspects unclear for a mutation tool.

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 a single, efficient phrase: 'Revert pending network changes'. It's front-loaded with the core action and target, with zero wasted words. This is appropriately concise for a tool with a simple purpose and one parameter.

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?

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It lacks details on what 'pending network changes' are, the revert's effect on node operations, error conditions, or return values. For a tool that could impact network configuration, this minimal description is insufficient.

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 schema description coverage is 100%, with the single parameter 'node' clearly documented as 'Node name'. The description doesn't add any parameter-specific information beyond the schema, but with only one well-documented parameter, the baseline is high. A score of 4 reflects that the schema adequately covers the parameter semantics without needing extra description.

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 'Revert pending network changes' clearly states the action (revert) and target (pending network changes), but it's somewhat vague about scope and mechanism. It doesn't specify what 'pending network changes' are or how they differ from applied changes, nor does it distinguish from sibling tools like 'pve_apply_node_network' beyond the verb difference.

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 provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., that pending changes must exist), consequences of reverting, or when to choose this over 'pve_apply_node_network' (which likely applies pending changes). Without this context, an agent might misuse the tool.

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