zpa_get_server_group

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

The description merely repeats the read-only hint already present in annotations and adds no extra behavioral context—no return shape, error semantics, authentication requirements, or microtenant scope behavior.

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?

A single brief sentence is tightly front-loaded and conveys action, resource, and scope with zero filler.

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 read-only get-by-id tool this is minimally viable, but with no output schema or parameter descriptions, it leaves return-value shape and microtenant semantics unexplained.

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 0%, and the description does not compensate by explaining the role of group_id or microtenant_id beyond their self-evident names and schema titles.

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?

Description uses a specific verb ('Get'), names the resource ('ZPA server group'), and signals singular scope ('one'), clearly distinguishing it from zpa_list_server_groups and other ZPA get/list siblings.

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?

'Get one' implies this is for retrieving a single group by ID when the caller knows which group is needed, but the description never explicitly contrasts it with zpa_list_server_groups or states exclusions.

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