List Firewall Rules

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

Description adds filtering and pagination behavior beyond annotations (readOnly=true, etc.). Does not contradict annotations. No side effects mentioned but annotations already cover safety.

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?

Two concise sentences front-loading the primary action. Every word contributes meaning; no filler or tautology.

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?

With full schema coverage and safety annotations, the description adequately captures functionality. No output schema exists, so omission of return details is acceptable.

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 coverage is 100% with detailed descriptions. Description reiterates parameters (chain, disabled, limit, offset) but adds no new semantic information beyond the schema.

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 verb 'List' and resource 'firewall rules' with specific scope 'from the filter or nat table on a MikroTik router'. Differentiates from sibling 'manage_firewall_rule' which handles mutations.

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?

Provides clear context for usage (listing firewall rules with filtering and pagination) but lacks explicit when-not-to-use or alternative tools. However, the purpose is unmistakable among siblings.

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