ztw_list_ip_destination_groups_lite

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

The description adds the behavioral detail that it is read-only and uses a lighter endpoint, which complements the readOnlyHint annotation. It does not contradict annotations. However, it does not disclose other behavioral aspects like pagination, rate limits, or the exact nature of the 'lite' endpoint beyond being lighter, so it provides only modest additional context beyond the annotation.

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, consisting of two short sentences that state the purpose and the key distinction from the sibling tool. It is front-loaded with the core action and read-only nature, and every word earns its place. No fluff or redundancy.

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 has no output schema and only two parameters (one well-documented in the schema, one undocumented), the description is somewhat minimal. It clarifies the relationship to the non-lite sibling and the read-only nature, but it does not describe the return format, any limitations of the lite endpoint, or the meaning of `exclude_type`. For a simple list tool with good annotations, this is adequate but not fully complete.

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 description does not explain the parameters directly, but the input schema provides detailed documentation for the `query` parameter, including examples and important caveats about field naming. The `exclude_type` parameter has no description in the schema, and the description does not compensate for that gap. With 50% schema coverage, the description adds no parameter semantics, but the schema's rich `query` documentation partially mitigates the gap. The lack of any description for `exclude_type` is a notable deficiency.

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 tool lists ZTW IP destination groups via a lighter SDK endpoint and explicitly notes it is read-only. It distinguishes itself from the sibling tool `ztw_list_ip_destination_groups` by mentioning it uses the lite endpoint and returns the same records, which helps differentiate it from the non-lite variant.

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 implies usage context by noting it is the lighter endpoint and returns the same records as the full version, suggesting it is a lighter alternative. However, it does not explicitly state when to prefer this over the non-lite version or other listing tools, nor does it mention any exclusions or alternatives beyond the sibling tool.

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