zia_list_location_groups

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

With readOnlyHint=true and no output schema, the description adds nothing beyond the annotation. It does not disclose pagination behavior, result format, or any filtering defaults. The word 'List' aligns with the read-only hint but offers no extra behavioral context.

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—a single sentence with no wasted words. However, given the tool's simplicity, this brevity is appropriate, though it might benefit from a brief mention of filtering options to aid the agent.

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 listing tool with three parameters, no output schema, and a readOnly annotation, the description is too sparse. It does not mention what a location group is, how results are ordered, or how to combine parameters. The detailed query param guidance lives in the schema, but the overall tool description leaves significant gaps for an agent to operate 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 input schema has only 33% description coverage (only 'query' has a detailed explanation). The tool description 'List ZIA location groups' provides no parameter information, failing to compensate for the low schema coverage. Parameters 'name' and 'search' remain unexplained in the description.

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 location groups' clearly states the action (list) and the resource (ZIA location groups), distinguishing it from related tools like zia_get_location_group or zia_list_locations. The purpose is unambiguous and immediately actionable.

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 such as zia_get_location_group for a single group or zia_list_locations for locations. There is no mention of prerequisites, frequency, or trade-offs, leaving the agent to infer usage solely from the name.

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