OPNSense MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool tests connection and authentication, implying a read-only, non-destructive operation, but doesn't specify what 'test' entails (e.g., returns success/failure, error details, latency metrics) or any side effects (e.g., logging, rate limits). For a tool with zero annotation coverage, this leaves key behavioral aspects unclear.

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 with the core purpose and appropriately sized for a simple tool. Every part of the description ('Test API connection and authentication') earns its place by conveying essential information.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It covers the basic purpose but lacks details on usage context, behavioral output, or error handling. For a connection-testing tool in a server with many configuration siblings, more completeness would help the agent understand when and how to invoke it effectively.

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, and schema description coverage is 100% (though empty). The description doesn't need to explain parameters, so it meets the baseline. No additional parameter information is required or provided, which is appropriate for a parameterless tool.

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 'Test API connection and authentication' clearly states the tool's purpose with a specific verb ('Test') and target ('API connection and authentication'). It distinguishes this from sibling tools that perform configuration, management, or query operations. However, it doesn't explicitly differentiate from potential alternative connection-testing tools (though none are present in the sibling list).

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. It doesn't mention prerequisites (e.g., use after configuration), typical scenarios (e.g., verify setup before other operations), or exclusions. With many sibling tools for various operations, the lack of contextual guidance is a significant gap.

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