zia_list_workload_groups

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

The annotation 'readOnlyHint: true' already indicates a read-only operation, and the description is consistent with that. The description adds no additional behavioral context beyond what the annotation provides, which is acceptable but not enriching.

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 very concise (one short sentence), but it lacks structure and detail. While it avoids verbosity, it is so brief that it may not provide sufficient information for proper tool selection and use.

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 operation, the description conveys the core purpose. However, it omits details about pagination (implied by schema parameters), filtering via JMESPath, and the relationship to the sibling tool for getting a single workload group. Given the absence of an output schema, more context would be beneficial.

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?

The tool description does not explain any parameters; it only repeats the tool name's action. The schema covers 33% of parameters (the 'query' parameter has a description), but the tool description adds no value for the other two parameters ('page' and 'page_size').

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 'List' and the resource 'ZIA workload groups', making the basic purpose obvious. However, it does not explicitly distinguish this tool from its sibling 'zia_get_workload_group' (which retrieves a single group), though the name implies the difference.

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 or filtering, and no conditions for use. It simply states the action without context.

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