get_zia_dlp_dictionaries

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

The description confirms the read-only nature (matching annotations) and outlines two distinct behaviors. It does not contradict annotations. Additional details like rate limits or edge cases are absent, but the core behavior is clear.

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, front-loaded sentence that efficiently conveys the tool's purpose and key usage modes with no wasted 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 covers the main use cases but omits details on return format (no output schema) and the 'search' parameter. For a simple read tool, this is adequate but not fully complete given the parameter count and low schema coverage.

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 low (25%); the description adds high-level semantics ('list all/lite' maps to action, 'fetch by ID' maps to dict_id) but does not explain the 'search' or 'query' parameters beyond the schema's own description of query. This partially compensates for the low coverage.

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 'Read' and the resource 'ZIA DLP dictionaries', and specifies two distinct use cases: listing all/lite and fetching by ID. This distinguishes it from sibling tools like 'get_zia_dlp_engines'.

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 when to use each action (list vs fetch by ID) and explicitly marks the tool as 'read-only'. However, it does not provide explicit alternative tools or conditions when not to use.

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