zia_get_web_dlp_rule

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

The description only states the action 'Get' which aligns with the readOnlyHint annotation. It does not disclose any side effects, error behavior, or prerequisites, so it adds minimal transparency beyond the 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?

The description is a single concise sentence, front-loaded with the verb 'Get' and the object 'single ZIA Web DLP rule'. It is appropriately sized with no unnecessary words.

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 description lacks details about the response format, error handling, or any prerequisites. While it is a simple get operation, it could benefit from more context such as what 'member references' includes, but the minimalism is acceptable for this type of tool.

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 description clarifies that the rule_id parameter is the ID of the rule to fetch, which adds a small amount of meaning. However, it does not provide additional details like format or constraints.

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 indicates that the tool retrieves a single ZIA Web DLP rule by its ID, distinguishing it from sibling list operations. It also mentions 'member references', suggesting additional response details, but the core purpose is clear.

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?

The description does not explicitly state when to use this tool versus alternatives, such as when an ID is known. It only describes the action without usage context.

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