zia_list_cloud_firewall_dns_rules

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

Annotations already declare readOnlyHint=true, so the description adds no behavioral context. It does not mention pagination, rate limits, or what happens if no rules exist. The description is minimal and does not enhance transparency beyond the 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 sentence, which is concise but not appropriately sized. It lacks informative content and does not justify its length; it essentially repeats the tool name. A good description should provide value beyond the name.

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 is a list operation with no output schema, the description should explain what the list contains, default behavior, or how results are ordered. It provides none of this. Sibling tools are many but not referenced for differentiation.

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 50%; only the 'query' parameter is described. The 'search' parameter is left undocumented. The description does not compensate by explaining 'search' or adding meaning beyond the schema. The purpose of listing DNS rules implies filtering, but no semantics are added.

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 'List' and the resource 'ZIA Cloud Firewall DNS rules'. It distinguishes from sibling tools like 'zia_list_cloud_firewall_rules' by specifying DNS rules, but lacks detail on the scope or what the list contains.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like 'zia_get_cloud_firewall_dns_rule' or other list tools. No when-not-to-use or context is given.

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