proxmox_guest_firewall_rule

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

No annotations are provided, so the description carries full burden. It only mentions 'elevated' for mutation actions, hinting at permission requirements. It does not disclose side effects (e.g., immediate rule enforcement), idempotency, error behavior, or any other behavioral traits. This is insufficient for a 20-parameter 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 two sentences: a broad statement then specificity. It is relatively concise but could be more structured (e.g., grouping parameters). The first sentence front-loads the core purpose. While not verbose, it is dense and could sacrifice clarity for brevity.

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 tool with 20 parameters and no annotations or output schema, the description is incomplete. It lacks information on rule ordering, effect of changes, return values, and common usage patterns. Basic completeness for query and mutation operations is provided, but many important aspects are missing.

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 low (30%). The description adds meaning for key parameters like rule_action, rule_type, action, and type, explaining their roles (e.g., 'Uses rule_action for firewall action (ACCEPT/REJECT/DROP)'). However, most other parameters (pos, comment, dest, dport, etc.) are left unexplained. The description compensates only partially for the low coverage.

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 clearly states the tool manages per-guest firewall rules, and differentiates query (list/get) vs mutation (create/update/delete) actions. It implicitly distinguishes from cluster-level firewall rule tools in the sibling list (proxmox_cluster_firewall_rule). The purpose is specific and actionable.

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 provides guidance on action choice based on intent (query vs manage) and hints at elevated permissions for mutations. However, it does not explicitly mention when not to use this tool (e.g., for cluster-wide rules) or compare with alternatives. The guidance is present but incomplete.

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