zia_list_cloud_firewall_ips_rules

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

Annotations declare readOnlyHint=true, covering the safety profile. The description adds no extra behavioral context such as pagination, ordering, or response structure. It is a minimal statement with no additional disclosures beyond the action itself.

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 concise sentence, front-loaded with the purpose. There is no fluff, but it is perhaps too terse to provide useful details while remaining efficient. It earns its place but could be more informative without losing 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?

With no output schema and two parameters, the description lacks completeness. It does not mention what the response contains, any filtering behavior, or clarify the 'search' parameter. The tool is simple, but the description leaves too much undefined for an agent to use it confidently.

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% (query has detailed description, search has none). The tool description adds no parameter information at all. It does not compensate for the undocumented 'search' parameter, leaving its meaning ambiguous.

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 ZIA Cloud Firewall IPS rules' clearly states the action (list) and the resource (ZIA Cloud Firewall IPS rules). It distinguishes from sibling tools like 'zia_list_cloud_firewall_rules' or 'zia_list_ips_signature_rules' by specifying 'IPS rules' under cloud firewall.

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 exclusions, prerequisites, or alternative tools for filtering or different scopes. It only states a basic function without context.

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