get_zia_dlp_engines

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

The annotations already declare readOnlyHint=true, so the agent knows it's a safe read operation. The description adds the ability to list or fetch by ID, but does not provide additional behavioral details such as default behavior, data volume, or authentication requirements. No contradiction with 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 sentence, concise and front-loaded. However, it sacrifices detail for brevity, leaving the agent to guess about parameter usage and distinctions between modes.

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 completeness for a tool with 4 parameters and no output schema. It does not explain the return structure, the difference between full and lite results, or how the search parameter works. The agent would need additional information to use the tool effectively.

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 low (25%), and the tool description does not provide additional parameter semantics. It vaguely implies the roles of action and engine_id but does not explain them in detail, leaving the agent to infer from the parameter names and enum values.

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 resource 'ZIA DLP engines', and outlines two modes: listing all/lite or fetching by ID. However, it does not clarify the difference between 'all' and 'lite' modes, which could cause confusion.

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 guidance is provided. The description does not indicate when to use this tool compared to similar tools like get_zia_dlp_dictionaries, nor does it explain when to choose 'read' versus 'read_lite' action. The agent receives no contextual selection criteria.

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