router_nftables_rules

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context by specifying that it shows 'active' rules (not just configured ones) and that the view is 'filtered' and 'paginated', which goes beyond the annotations.

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 one efficient sentence that front-loads the verb and resource, includes key qualifiers ('filtered', 'paginated', 'read-only', 'active'), and contains no filler or redundancy.

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?

The tool has 5 undocumented parameters and no output schema, so a complete description would need to explain parameter relationships and the return shape. While the description names the resources and mentions filtering/pagination, it lacks details on how filters interact, pagination defaults, or what the output contains, making it adequate but not 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?

Schema description coverage is 0% for 5 parameters, so the description must compensate by explaining their meaning. It only hints at 'filtered' and 'paginated' behavior without mapping them to the chain, table, family, limit, and offset parameters, leaving the agent to infer which parameters correspond to which behavior.

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 uses a specific verb ('Get') and a precise resource ('active nftables rules, sets, maps, and counters'), which clearly distinguishes it from sibling tools like router_firewall_status or router_routes. The qualifier 'filtered, paginated read-only view' further clarifies the tool's exact 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?

The resource name and description imply the tool is for nftables-related inspection, but there is no explicit statement of when to use this tool vs alternatives, nor mention of any exclusions. Sibling tools like router_firewall_status could overlap conceptually, and no guidance is given to differentiate them.

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