create_firewall_rule_advanced

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

The WARNING that 'This modifies the running firewall configuration' adds behavioral context beyond the readOnlyHint=false annotation, alerting the agent to mutation of a live system. However, it doesn't disclose potential traffic disruption, the default of apply_immediately=true, or other side effects that could affect network connectivity.

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?

Two concise sentences: a clear purpose statement and a necessary warning. No filler or redundant information. The structure is front-loaded and efficient.

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 complex 15-parameter mutation tool, the description is minimal. It lacks preconditions, side effects, or relationship to apply_firewall_changes. However, the rich schema and output schema compensate significantly, leaving only moderate gaps in high-level 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 100%, so the schema already documents all 15 parameters with formats, defaults, and semantic notes (e.g., position rule created first then moved). The description adds no parameter-specific meaning, so the baseline score of 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?

The description clearly states 'Create a firewall rule on the live pfSense appliance', using a specific verb and resource. It naturally distinguishes from sibling tools like update_firewall_rule, delete_firewall_rule, and move_firewall_rule. Although the 'advanced' suffix isn't explained, the core purpose 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?

The description provides no explicit guidance on when to use this tool versus alternatives like update_firewall_rule or move_firewall_rule. It doesn't mention prerequisites, when not to use it, or how it relates to apply_firewall_changes. The warning implies caution but does not direct tool selection.

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