zia_list_web_dlp_rules_lite

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

Annotations already provide readOnlyHint=true; the description reinforces 'read-only'. It adds JMESPath client-side filtering, which is a key behavioral trait. However, it does not disclose other behaviors like pagination, rate limits, or data freshness beyond what annotations indicate.

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?

A single sentence that efficiently conveys the tool's purpose, format, read-only nature, and client-side filtering capability. Every word adds necessary information without redundancy.

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 and annotations covering safety, the description provides sufficient context: it tells what is listed, that the operation is safe, and the filtering mechanism. The only minor gap is the unspecified 'lite format' details, but those are likely documented in the output schema.

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% with per-parameter descriptions. The description adds value for the 'query' parameter by specifying JMESPath filtering, but provides no additional insight for 'search' or 'service' parameters, which are adequately described in the schema.

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), resource (ZIA web DLP rules), and format (lite, read-only). It distinguishes from full listing tools by the 'lite' modifier, but does not explicitly explain what 'lite' entails or contrast with the sibling tool 'zia_list_web_dlp_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?

No guidance on when to use this tool versus alternatives like 'zia_list_web_dlp_rules' or 'zia_get_web_dlp_rule'. The description does not mention prerequisites, performance considerations, or exclusions, leaving the agent without context for situational selection.

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