panorama_never_matched_rules

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

No annotations are provided, so the description must carry full behavioral transparency. It mentions returning a dict with lists and analysis details, but does not disclose whether the tool is read-only, performance impact, or any side effects. Minimal behavioral context beyond the purpose.

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 main sentence is front-loaded and clear. The Args/Returns sections add structure but are somewhat redundant with the in-line parameter descriptions. Could be more concise by integrating parameter explanations into the main 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?

Parameters are documented, and the return type is described. However, missing context such as what constitutes a 'security rule', definition of 'never matched', and no examples. Given 3 parameters and no output schema, the description is adequate but not fully complete.

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 input schema has 0% description coverage, but the description includes 'Args' section with docstrings for 'device_group', 'days', and 'limit', explaining their meaning and defaults. This compensates well for the missing schema descriptions.

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 starts with 'Find security rules that never matched traffic' – a clear verb+resource pair. It distinguishes from siblings like 'panorama_security_rules_analysis' (broader) and 'panorama_rules_without_profile' (different criterion).

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 states the tool's purpose but does not provide explicit guidance on when to use it versus alternatives, prerequisites, or when not to use it. Usage is implied but not spelled out.

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