zia_list_workload_groups

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear. However, the description adds no behavioral detail beyond the action itself—no mention of pagination behavior, result limits, output shape, or potential large payloads. With no additional context, the agent is left to infer behavior from the parameter schema alone.

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, direct sentence with no fluff or redundancy. It earns its place by efficiently naming the operation and resource.

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 list tool, the description is minimal but leaves out important contextual details: no usage guidance, no pagination semantics, and no output/return behavior. The rich 'query' parameter description is buried in the schema, but the overall tool definition does not give enough context for confident selection and invocation among many similar ZIA list tools.

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 only 33%; only the 'query' parameter is described in detail, and it is indeed helpful. However, 'page' and 'page_size' lack any explanation of defaults, indexing, or limits, and the tool description itself does not compensate for these gaps.

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 'List ZIA workload groups' uses a specific verb ('List') and resource ('ZIA workload groups'), clearly distinguishing it from the sibling 'zia_get_workload_group' tool. It is instantly clear what the tool does.

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 provides no guidance on when to use this tool versus alternatives, no mention of pagination, and no hint about whether to use zia_get_workload_group for single-item retrieval. There is no 'when to use' or 'when not to use' context.

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