ztw_list_network_service_groups

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

The annotation readOnlyHint already indicates read-only behavior; the description repeats this without adding new behavioral insights (e.g., pagination, rate limits, result structure). The openWorldHint=false annotation is not explained.

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 sentence, making it concise. However, it is too brief to be maximally useful; a bit more detail would not harm conciseness.

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?

The description is incomplete for a tool with an undocumented parameter and no output schema. It fails to explain what network service groups are or how to filter them via the 'search' parameter, which is essential for correct use.

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 schema describes the 'query' parameter, but the 'search' parameter is undocumented (0% description in schema) and the description mentions neither parameter. An agent would not understand how to use 'search'.

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' and the resource 'ZTW network service groups', and the '(read-only)' suffix reinforces safety. However, it does not distinguish from the similar sibling 'zia_list_network_svc_groups', which could cause confusion for an AI agent.

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. Given the large number of sibling list tools, explicit context is needed but missing.

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