zia_list_ip_destination_groups

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

Annotations already declare readOnlyHint=true, so the tool is known to be safe and read-only. The description adds no further behavioral context (e.g., results format, pagination, or side effects), but does not contradict annotations.

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 short (5 words), which undermines utility. While concise, it is under-specified and omits critical information that should be present.

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 tool is a list operation with no output schema and many siblings, the description is incomplete. It fails to mention the available filtering via the 'query' parameter, existence of a get counterpart, or the scope of results (e.g., 'all groups' vs. filtered).

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 coverage is 50%—only 'query' has a description in the schema, which is helpful. However, the tool description itself adds no information about parameters (e.g., what 'search' does) and does not compensate for the missing schema description of the second parameter.

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 resource 'ZIA IP destination groups', making the purpose explicit. However, it does not differentiate from sibling tools like 'zia_get_ip_destination_group' (for a single group) or other list tools.

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 (e.g., zia_get_ip_destination_group for a specific group). There is no mention of prerequisites, context, or exclusions.

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