zia_get_cloud_firewall_dns_rule

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

Annotations already declare readOnlyHint=true and openWorldHint=false, establishing this as a safe read operation. The description adds the detail 'with member references,' hinting at response content, but does not elaborate on behavior for missing IDs or reference semantics. No contradiction with annotations.

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, front-loaded sentence with no redundant words. Every word contributes to identifying the tool's purpose and scope.

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, single parameter, and read-only annotations, the description is largely sufficient. It would benefit from clarifying return details beyond 'member references' and handling of nonexistent IDs, but the sibling list tool and annotations provide enough surrounding context.

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% and the only parameter is rule_id with just a 'Rule Id' title. The description says 'by ID,' which mirrors the parameter name but adds no additional guidance about format, source, or how to obtain a valid ID.

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 uses a specific verb ('Get'), names the exact resource ('ZIA Cloud Firewall DNS rule'), and scopes it to a single item 'by ID'. This clearly distinguishes it from the sibling list tool (zia_list_cloud_firewall_dns_rules) and other get_* tools.

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 phrase 'Get a single ... by ID' clearly indicates this tool is for retrieving one specific rule when its ID is known. It does not explicitly mention alternatives like listing rules to find an ID, but the context is clear and not misleading.

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