OPNSense MCP Server

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

With no annotations, the description carries full burden but lacks behavioral details. 'Apply' implies a mutation, but it doesn't disclose if it's destructive, requires specific permissions, has side effects, or involves rate limits. This is inadequate for a tool that likely modifies infrastructure.

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 sentence with no wasted words. It's front-loaded and appropriately sized for the tool's complexity, making it easy to parse quickly.

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 no annotations, no output schema, and a likely complex mutation operation (infrastructure deployment), the description is incomplete. It doesn't cover behavioral traits, return values, or error conditions, leaving significant gaps for an agent to understand the tool's impact.

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 both parameters ('planId' and 'autoApprove'). The description adds no meaning beyond this, such as explaining what 'apply' does with the plan or the implications of 'autoApprove'. Baseline 3 is appropriate as the schema handles parameter documentation.

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 'Apply a deployment plan' states the action (apply) and target (deployment plan), but it's vague about what 'apply' entails—whether it executes, validates, or deploys infrastructure changes. It doesn't differentiate from sibling tools like 'iac_plan_deployment' or 'iac_destroy_deployment', leaving ambiguity in scope.

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 on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., requiring a plan from 'iac_plan_deployment'), exclusions, or comparisons to siblings like 'iac_destroy_deployment', leaving the agent without context for selection.

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