list_firewall_rules

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does not state whether this returns paginated results, whether it includes disabled rules, whether it reflects a specific rule ordering, or whether the concept of 'firewall rules' here is legacy vs. modern rulesets. For a read/list tool, the absence of pagination or scoping caveats leaves meaningful behavioral gaps.

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, short sentence that conveys the essential action and target in five words. There is no filler, and the key scope constraint is present. It is concise without losing meaning.

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 one-parameter list tool with no output schema and no annotations, the description is minimal. It doesn't mention pagination, default limits, or whether the 'firewall rules' returned include legacy firewall rules versus rulesets. Given the massive sibling list with closely related tools (list_zone_rulesets, get_waf_custom_rules, list_filters), the description lacks the context needed to reliably distinguish and use the tool.

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%, and the only parameter, zone_id, already has a description ('The zone ID'). The tool description adds the contextual relationship between the parameter and the resource ('for a zone'), but that is otherwise clear from the tool name and schema. Baseline 3 applies because the schema fully documents the parameter.

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 'List firewall rules for a zone' has a clear verb ('List') and resource ('firewall rules for a zone'), and the singular required parameter zone_id reinforces the scope. It doesn't differentiate from similar zone-scoped list tools like list_zone_rulesets or get_waf_custom_rules, but those are distinct enough by name that the core purpose is unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as list_zone_rulesets, get_waf_custom_rules, or list_filters. There are no context cues, prerequisite notes, or exclusions, so an agent choosing among many firewall-related list tools gets no assistance.

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