zia_list_web_dlp_rules

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

Annotations already declare `readOnlyHint: true`, and the description redundantly states 'read-only'. It adds the behavioral trait of JMESPath filtering support, which is useful. 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?

Extremely concise (one sentence) and front-loaded with purpose. However, it omits potentially useful context such as typical use cases or output structure, making it slightly under-informative.

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?

With an output schema present, the description does not need to explain return values. However, for a tool with many siblings and optional parameters, it lacks guidance on filtering options or when to use `search` vs `query`. Adequate but not comprehensive.

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 baseline is 3. The description adds no new parameter meaning beyond the schema; it merely echoes the JMESPath capability already described in the `query` parameter's schema description.

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?

States it lists ZIA web DLP rules and is read-only. The verb 'List' and resource 'web DLP rules' are clear. However, there is no differentiation from sibling tools like `zia_list_web_dlp_rules_lite` or `get_zia_web_dlp_rule`, which limits distinction.

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 guidance on when to use this tool versus alternatives. Does not mention that for a single rule one should use `get_zia_web_dlp_rule` or that the 'lite' variant exists for lighter results. No prerequisites or context provided.

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