zia_list_web_dlp_rules_lite

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

Annotations already provide readOnlyHint=true, so no contradiction. The description adds minimal behavioral context (uses a lighter endpoint) but does not disclose potential limitations like reduced fields or performance characteristics. With annotations covering safety, a 3 is appropriate.

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 with no unnecessary words. It directly states the purpose and key differentiator. All information is earned.

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?

Apart from the lighter endpoint hint, there is no explanation of what the lighter version returns compared to the full list, nor any mention of response structure or pagination. With no output schema, the description should provide more context about the results. It is minimally adequate.

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% (query parameter described well, search parameter missing). The tool description does not add any additional parameter information beyond the schema. Given the partial coverage, a baseline of 3 is correct.

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 (List), the resource (ZIA Web DLP rules), and distinguishes from siblings by mentioning 'via the lighter SDK endpoint'. This is specific and helps differentiate from the full list endpoint or get rule tool.

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 vs the non-lite version or alternatives. The phrase 'lighter SDK endpoint' implies a difference but does not specify when to prefer this tool over 'zia_list_web_dlp_rules' or other list tools.

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