zpa_list_server_groups

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

The description labels the tool as 'read-only', which aligns with the annotation (readOnlyHint=true) and provides basic transparency. However, it does not disclose other behavioral traits such as pagination behavior (though pagination params exist in schema) or any authorization requirements beyond what annotations imply.

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, well-structured sentence with no wasted words. It efficiently communicates the core purpose and key feature (JMESPath filtering).

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 output schema exists, the description does not need to detail return values. It covers the essential listing functionality and filtering support. Minor gap: it doesn't explicitly state that results are paginated (though parameters indicate this) or that no parameters mean all results. Still, it is largely complete for a read-only list tool.

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?

With 100% schema coverage and detailed parameter descriptions, the description adds no new meaning beyond stating JMESPath support (already in schema's query param description). Baseline 3 is appropriate as the schema carries the semantic load.

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 tool's verb (List), resource (ZPA server groups), and read-only nature. It distinguishes from sibling tools like 'zpa_get_server_group' by indicating it lists multiple items, and from other list tools by specificity to server groups.

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 mentions JMESPath client-side filtering but provides no guidance on when to use this tool versus other list tools (e.g., zpa_list_app_connector_groups). No explicit when-to-use, when-not-to-use, or alternative recommendations.

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