OPNSense MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Get ARP table statistics' implies a read-only operation but provides no information about authentication requirements, rate limits, response format, or whether this returns aggregated data versus raw entries. The description is too minimal for a tool with no annotation coverage.

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 extremely concise at just three words, with zero wasted language. It's front-loaded with the essential action and resource, making it immediately understandable at a basic level. Every word earns its place in this minimal description.

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 complexity of network management tools and the lack of both annotations and output schema, the description is insufficient. 'Get ARP table statistics' doesn't explain what format the statistics come in, what specific metrics are included, or how this differs from the multiple ARP-related sibling tools. For a tool in this domain with rich sibling alternatives, more context is needed.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the parameter situation. The description doesn't need to compensate for any parameter gaps. The baseline for this scenario is 4 since the description doesn't add parameter information but doesn't need to given the complete schema coverage for zero parameters.

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 'Get ARP table statistics' clearly states the action ('Get') and resource ('ARP table statistics'), providing a basic understanding of what the tool does. However, it doesn't differentiate from sibling tools like 'list_arp_entries' or 'find_arp_by_*' tools, leaving ambiguity about what specifically distinguishes this tool from those alternatives.

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 guidance on when to use this tool versus alternatives. With multiple ARP-related sibling tools (list_arp_entries, find_arp_by_hostname, find_arp_by_interface, find_arp_by_ip, find_arp_by_mac), the agent receives no indication of whether this tool provides summary statistics versus detailed entries, or what context would make this the appropriate choice.

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