ztw_list_ip_destination_groups

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

The description notes 'Read-only', but this is redundant with the readOnlyHint annotation. It adds the behavioral detail of exclude_type filtering, but does not disclose other behaviors such as pagination, return format, or potential errors. With annotations covering the read-only nature, the description adds marginal value beyond that.

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 two short sentences, front-loaded with the main purpose, and every word adds value. It avoids repetitions and clearly integrates the key parameter usage without bloat.

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 simple list operation with two optional parameters and readOnlyHint provided, the description covers the essential aspects: what it does, a key parameter, and read-only nature. It does not explain return structure, but without an output schema and given the simple nature, this is adequate. A note on when to use the lite version would improve completeness, but it's not a major gap.

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 50%, and the description compensates by clarifying exclude_type's purpose with an example. The query parameter already has a detailed schema description, so the tool description's additional value for parameters is focused on exclude_type, which is helpful but not exhaustive.

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 'List ZTW IP destination groups' with a specific verb and resource, and the name includes 'list' and 'ip_destination_groups' which distinguishes it from other list tools like the lite version. It also mentions the exclude_type parameter, adding specificity.

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?

It gives a concrete usage example for exclude_type ('omit a group type e.g. exclude DSTN_FQDN'), which provides clear context for when to use the parameter. However, it does not explicitly compare with alternatives like the lite version or other group-list tools, so it lacks exclusions or differentiation guidance.

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