zia_get_cloud_firewall_dns_rule

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

The description reiterates the readOnly annotation ('read-only') but adds minimal behavioral context beyond what annotations already provide. No mention of rate limits, authorization, or side effects. However, since annotations cover read-only, the description is adequate for the tool's simplicity.

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 of 12 words, front-loading the core purpose. No redundant or wasted words. It is highly concise.

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 no output schema and good annotations, the description is nearly complete. It could explicitly state that it returns the full rule object, but this is not essential given the tool's straightforward nature.

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%, so the description adds no additional meaning to parameters beyond the schema's existing descriptions. The schema already explains rule_id and service parameters.

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 specific resource 'ZIA cloud firewall DNS rule', and the scope 'by ID (read-only)'. It distinguishes this tool from siblings like 'zia_get_cloud_firewall_rule' which is for non-DNS rules.

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 versus alternatives. It mentions 'by ID' but lacks guidance on when to prefer this over listing tools like 'zia_list_cloud_firewall_dns_rules'. No exclusions or alternative tools are referenced.

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