zia_list_cloud_firewall_dns_rules

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

The description is consistent with readOnlyHint=true and does not contradict annotations, so the safety profile is clear. However, it adds no behavioral context beyond that: no pagination, response shape, result scope, or field-format caveats are disclosed in the description 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 one short, front-loaded sentence with no filler or redundancy. Every word carries meaning and the structure is clear.

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 low-complexity read-only list with two optional parameters and no output schema, the description is minimally viable but incomplete: it does not state return format, pagination behavior, or what fields a DNS rule record contains. The detailed query parameter docs partially compensate, but the short description alone leaves gaps.

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?

The tool-level description does not describe either parameter. The query parameter is well documented in the schema, but the search parameter has no description and schema coverage is only 50%; the description does nothing to clarify the ambiguous 'search' field.

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 is a specific verb+resource statement: 'List ZIA Cloud Firewall DNS rules.' It clearly distinguishes from siblings such as zia_get_cloud_firewall_dns_rule (single-rule retrieval) and zia_list_cloud_firewall_rules (general firewall 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 provides no when-to-use guidance, exclusions, or alternative recommendations. It does not point to zia_get_cloud_firewall_dns_rule for individual lookups or explain when search/query parameters are appropriate; usage is only implied by the verb 'List.'

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