linux_iptables_rule_generator

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

Description adds value beyond annotations: explains it is read-only, non-destructive, rate-limited, validates IPs/ports, emits lockout warnings. Annotations already indicate readOnlyHint true and destructiveHint false, but description enriches with specific details about rate limiting and validation.

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?

Description is thorough but somewhat dense. It front-loads the purpose and key characteristics, then covers usage, limitations, and return values. Could be slightly more concise, but no redundant sentences.

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 complexity (6 parameters, nested objects, output schema), the description is complete. It covers return format (scripts plus explanations, warnings, file paths), validation, lockout warnings, and presets. Output schema exists but description supplements it well.

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% with clear property descriptions. The description adds context like silent skip of invalid rows, presets operation behavior, and lockout warnings, which enhance understanding beyond the schema. Baseline 3 due to high coverage, plus extra context justifies 4.

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?

Clearly states the tool generates iptables-restore and nftables firewall scripts from a structured description, with specific verb 'Generate' and resource 'firewall scripts'. Distinguishes from sibling linux_ssh_config_generator by explicitly mentioning what it does not do.

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?

Explicitly states when to use ('author Linux netfilter rulesets') and when not ('use linux_ssh_config_generator instead for ssh_config and sshd_config'). Provides context that it only emits text and never runs iptables, with rate limits and validation behavior.

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