zpa_list_segment_groups

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

Annotations already declare readOnlyHint=true; the description reiterates read-only and adds the client-side filtering behavioral trait. However, it does not disclose pagination behavior, rate limits, or authentication requirements. The added value over annotations is moderate.

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 with two sentences, front-loading the purpose and a key feature. Every word earns its place; no 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?

Given the presence of an output schema and full parameter documentation, the description is adequate. It covers the core functionality and filtering. Minor omission: it doesn't state that the tool lists all segment groups in the tenant (implicit from 'List'), but overall complete enough for selection and invocation.

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, the input schema already fully documents parameters. The description only mentions the 'query' parameter for JMESPath, adding no new semantics beyond what is in the schema. Baseline for high coverage is 3.

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', the resource 'ZPA segment groups', and notes read-only nature. It also mentions JMESPath filtering. While it doesn't elaborate on what a segment group is, the purpose is specific and distinguishable from sibling tools that list other ZPA resources.

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 some usage guidance by noting JMESPath client-side filtering support, which helps decide when to use this tool. However, it lacks explicit 'when not to use' or alternatives among the many sibling list tools, leaving the agent to infer the appropriate context.

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