zia_list_device_groups

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

The readOnlyHint annotation already declares this as read-only, but the description adds no extra behavioral context—no mention of return format, pagination, or any side effects. Given the annotation, the bar is lower, but the description contributes nothing beyond the annotation.

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 extremely concise and front-loaded with the core purpose. There is no wasted text. However, it is so brief that it borders on under-specification, but the single sentence is clear and efficient.

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 listing tool with three optional parameters and no output schema, the description is inadequate. It omits any details about what the parameters do, what the response looks like, or any caveats, making it incomplete for an agent to use 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?

The description provides zero information about the three parameters. Schema coverage is only 33% (only 'query' has a description), and the description fails to compensate for the undocumented 'include_device_info' and 'include_pseudo_groups' parameters, leaving them unexplained.

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 device groups.' clearly states the action (list) and resource (device groups) with a specific product context (ZIA). It is unambiguous, though it doesn't distinguish from many sibling list tools except by resource name.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, filtering options, or comparison with similar tools like zia_list_devices or zid_list_groups.

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