opnsense_nat_apply

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

With no annotations provided, the description includes 'DESTRUCTIVE.' to warn of potential impact. This goes beyond a simple description, though it does not detail what exactly is destructive.

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 sentences, front-loaded with the core action and immediate context. No unnecessary words.

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 simple parameter and no output schema, the description is fully complete: it explains the purpose, usage context, and behavioral warning.

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 single parameter 'confirm' is self-explanatory from the schema (boolean with enum [true]). The description adds no value beyond the schema, but the schema coverage is 0% because the parameter isn't documented in the 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 clearly states 'Apply pending NAT configuration changes' with the verb 'apply' and resource 'NAT configuration'. It distinguishes from sibling tools like opnsense_nat_source_add by focusing on applying changes rather than individual management.

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?

Explicitly states 'Required after add/update/delete/toggle for changes to take effect', providing clear when-to-use context. It does not mention when not to use, but the context is well covered.

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