get_zia_dlp_engines

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

Annotations already declare readOnlyHint=true, so the description's mention of 'read-only' adds confirmation but no new behavioral insights. No additional traits (e.g., pagination, error handling) are described.

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?

Single sentence, concise and front-loaded. However, the verb 'Manage' is slightly misleading for a read-only tool; 'Retrieve' would be more accurate. No extra fluff.

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 simple read-only nature, good schema coverage, and presence of annotations and output schema, the description is adequate but could be more specific (e.g., summarizing that it lists or retrieves engines by ID or search query).

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?

Input schema provides 100% description coverage, so the tool description adds little beyond the schema. The description's phrase 'Manage...' hints at the action parameter but does not explain semantics beyond schema.

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 states it manages ZIA DLP engines with a read-only note, clarifying the scope. The verb 'Manage' is broad but the parenthetical and annotation specify read-only. It distinguishes from sibling 'get_zia_dlp_dictionaries' by mentioning 'engines' specifically.

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 guidance on when to use this tool versus alternatives like 'get_zia_web_dlp_rule' or 'get_zia_dlp_dictionaries'. The description implies it's for reading DLP engine configurations but does not explicitly state when not to use it.

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