zia_get_cloud_firewall_rule

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

Annotations already declare readOnlyHint=true, so the agent knows it's a safe read. The description adds a small behavioral note ('with member references'), indicating the response includes related object references, which is useful but not extensive. No details on error handling or auth requirements are given.

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 that conveys the essential information without any unnecessary words. It is front-loaded with the purpose.

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 simple get-by-id tool with one parameter, the description gives adequate context: it specifies the resource type, the selection criteria, and hints at the response structure ('member references'). Since there is no output schema, the return format is not fully documented, but the description covers the primary usage scenario.

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 0%, so the description must compensate. It only says 'by ID,' which adds no meaning beyond the parameter name 'rule_id' already in the schema. There is no explanation of where to find the ID or any format constraints.

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 a specific action ('Get') on a specific resource ('a single ZIA Cloud Firewall rule') identified by ID. It distinguishes itself from sibling tools like zia_list_cloud_firewall_rules and zia_get_cloud_firewall_ips_rule by specifying 'Cloud Firewall rule' and 'single... by ID.'

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?

There is no guidance on when to use this tool versus alternatives, such as listing rules first to obtain an ID or when to choose the IPS rule variant instead. The context of needing a single rule by ID is implied but not explicitly stated.

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