zia_get_web_dlp_rule

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

The description adds 'read-only', consistent with the readOnlyHint annotation. No additional behavioral traits (e.g., error handling, rate limits) are disclosed, but annotations already cover the read-only aspect.

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, efficient sentence that conveys the core purpose with no filler. It could be more structured (e.g., bullet points) but is appropriately concise.

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?

For a simple retrieval tool with complete schema and annotations, the description is adequate. However, it lacks details about return format, pagination, or behavior on not-found, which would improve completeness.

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 has 100% description coverage for both parameters. The description does not add meaning beyond the schema; it only restates 'Get a specific ZIA web DLP rule by ID', which aligns with the rule_id parameter.

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 (Get), the resource (ZIA web DLP rule), and the method (by ID, read-only). It distinguishes from sibling listing tools like zia_list_web_dlp_rules by specifying 'specific' and 'by ID'.

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 implies use when needing a specific rule by ID but lacks explicit when-to-use, when-not-to-use, or alternative suggestions. Among many sibling tools, no differentiation guidance is provided.

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