firewall_list_rules

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

With no annotations, the description must carry the burden of behavioral disclosure. It provides the return type ('List of firewall rules with details') and names the input parameter, implying a read-only operation. However, it does not mention potential errors (e.g., invalid group ID), required permissions, pagination, or side effects, making it minimally informative rather than fully transparent.

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 brief, with a clear 'Args' and 'Returns' structure that is easy to parse. Every sentence earns its place, and there is no redundant phrasing. The example inline with the parameter is especially helpful without adding bulk.

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 the simplicity of the tool (one parameter) and the presence of an output schema, the description covers the essential invocation details: what the tool does, how to specify the group, and what to expect as a result. It does not mention how to obtain a group ID (e.g., via firewall_list_groups), but that is a minor omission for a well-scoped list operation.

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 description adds meaning beyond the bare schema (which only says 'type': 'string') by explaining that the parameter is 'The firewall group ID or description' and giving concrete examples like 'web-servers' or UUID. This is essential for correct invocation, especially since the schema has no description coverage.

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 states a specific action ('List all rules') on a specific resource ('firewall group'), which is clear and distinguishes it from tools like firewall_list_groups (which lists groups) and firewall_get_rule (which gets a single rule). However, it does not explicitly differentiate from sibling tools that also deal with firewall rules (e.g., lb_list_firewall_rules), so it stops short of a 5.

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?

No guidance is given on when to use this tool versus alternatives such as firewall_get_rule for a specific rule, firewall_list_groups to obtain group IDs, or lb_list_firewall_rules for load balancer firewall rules. The description simply states what it does without any conditions or exclusions.

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