zia_list_cloud_firewall_rules

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

The description is consistent with the readOnlyHint=true annotation and adds no conflicting information. However, it does not provide additional behavioral context (e.g., pagination, result limits, or sorting) beyond what annotations already imply. The description is simple and safe, but not rich.

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, clear sentence, which is concise and front-loaded. However, it is overly terse and adds little beyond the tool name, lacking any enriching details. It is not verbose but borders on under-specification rather than effective conciseness.

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 list tool with two optional parameters (one undocumented), no output schema, and only basic annotations, the description is too minimal. It omits any discussion of the search parameter or how results are structured, leaving gaps in what an agent needs to know for effective use.

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 50%, with the query parameter well-documented in the schema (including examples and warning about field naming), but the search parameter is completely undocumented. The tool description itself does not mention or explain either parameter, failing to compensate for the low coverage of search.

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 clearly states the tool lists ZIA Cloud Firewall rules, using a specific verb and resource. It distinguishes from sibling tools like zia_list_cloud_firewall_ips_rules and zia_get_cloud_firewall_rule by scope and action.

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. It does not mention any filtering, search, or context in which this list tool is preferred, leaving the agent without explicit usage directions.

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