zia_list_web_dlp_rules_lite

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

The `readOnlyHint` annotation already communicates safety, and the description adds no contradiction. The query parameter documentation provides valuable behavioral context: it warns that returned field names are snake_case, that guessing spellings can yield an empty list that looks valid, and advises calling once without `query` to inspect keys. These are useful beyond the annotation.

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 filler. Every word contributes to the core purpose, and the detailed schema documentation handles the complexity without bloating the tool description.

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?

The tool is a simple, read-only listing operation with helpful schema-level guidance, but the description does not explain what 'lighter' means, what fields are returned, or how this compares to `zia_list_web_dlp_rules`. Without an output schema, the definition would benefit from at least a sentence clarifying the lite variant's scope.

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 `query` parameter is richly described in the schema with JMESPath examples and a critical field-naming warning. However, the tool-level description adds no parameter meaning, and the `search` parameter has no description at all, leaving its syntax and interaction with `query` unclear.

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 action and resource: 'List ZIA Web DLP rules'. The phrase 'via the lighter SDK endpoint' hints at a distinction from the sibling `zia_list_web_dlp_rules`, but does not explain what 'lighter' means in terms of behavior or output.

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?

There is no explicit guidance on when to use this tool versus the closely related `zia_list_web_dlp_rules` or `zia_get_web_dlp_rule`. The 'lighter SDK endpoint' wording implies a lighter alternative but does not state the tradeoffs, prerequisites, or recommended use cases.

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