list_firewall_rules

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

The readOnlyHint annotation already signals a safe read operation, and the description is consistent with it. The phrase 'all firewall rules' adds mild behavioral context (returns a collection rather than a single rule), but the description does not disclose deeper behavior such as pagination or result ordering.

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, front-loaded sentence with no filler or redundant clauses. Every word contributes to identifying the action and scope.

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?

For a straightforward list operation with a well-documented schema and readOnly annotation, the description is minimally adequate. However, it omits guidance on optional behavior like filtering, depth, or what an empty result means, which the schema partially compensates for but the description does not address.

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%, so all five parameters are already documented in the input schema. The description adds no additional meaning beyond reflecting the role of nic_id ('on a network interface'), so it neither improves nor harms parameter understanding.

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 ('List') and identifies the exact resource ('firewall rules') plus scope ('on a network interface'), which clearly distinguishes it from the single-resource 'get_firewall_rule' and from rule-listing tools for other resource types like security groups or NAT gateways.

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 implies when to use the tool—when firewall rules for a specific NIC are needed—but it does not explicitly state alternatives, exclusion criteria, or when another sibling list tool would be more appropriate.

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