zia_get_cloud_firewall_rule

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

The description adds 'read-only', which aligns with the readOnlyHint annotation. It also clarifies that the key input is a rule ID. However, it does not disclose any additional behavioral traits such as error handling, performance, or prerequisites beyond what annotations already provide.

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 sentence that conveys the essential action efficiently. It is front-loaded with the verb and resource, but could incorporate brief context about when to use it without becoming verbose.

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 tool's low complexity (2 simple parameters, no output schema), the description provides the core functionality but lacks completeness. It does not mention potential errors, permissions, or relationship to other firewall rule tools like 'zia_get_cloud_firewall_dns_rule' or 'zia_get_cloud_firewall_ips_rule'.

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 coverage is 100% (both rule_id and service are described). The description adds no new semantic meaning beyond the schema's parameter descriptions, which is adequate given the 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 clearly states the verb ('Get'), the resource ('ZIA cloud firewall rule'), and the identification method ('by ID'). It distinguishes itself from sibling tools like 'zia_list_cloud_firewall_rules' by targeting a specific rule rather than a list.

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 does not explicitly state when to use this tool over alternatives. The read-only hint and the fact it retrieves a single rule imply use when a specific ID is known, but no guidance is given for when to prefer list-style tools or other get_* tools.

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