zia_list_web_dlp_rules

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds no behavioral details beyond a simple list operation; it does not disclose pagination, rate limits, or that results may be empty.

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 concise (one sentence), but it is too sparse, omitting useful information. It prioritizes brevity over completeness, which is acceptable for a simple list tool but still lacks depth.

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 lack of output schema and ambiguous 'search' parameter, the description does not provide enough context for effective tool use. It fails to differentiate from the 'lite' sibling or explain the 'search' parameter, making it incomplete.

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 50% because the 'search' parameter lacks a description. The tool description does not clarify 'search' or add meaning beyond the schema. The 'query' parameter is well-documented in the schema, but the overall parameter semantics are incomplete without explanation of 'search'.

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 uses a specific verb+resource ('List ZIA Web DLP rules'), making the purpose clear. However, it does not differentiate from the sibling 'zia_list_web_dlp_rules_lite', which likely serves a similar but distinct function.

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 (e.g., the 'lite' version), nor does it mention prerequisites or typical use cases.

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