ztw_list_ip_groups_lite

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. Description adds that it's a 'lighter SDK endpoint' suggesting performance advantage, but does not disclose any other behavioral traits (e.g., pagination, rate limits). No contradiction with 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?

Two concise sentences. First sentence states purpose and read-only nature. Second sentence provides key differentiator. No wasted words, well front-loaded.

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?

Tool is simple (2 optional params, no output schema). Description adequately covers purpose, differentiation, and read-only nature. With good annotations, the description is complete enough for correct 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?

Schema coverage is 50% (only `query` has description; `search` lacks description). The description does not mention either parameter, adding no meaning beyond the schema. This leaves the `search` parameter ambiguous for the agent.

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?

Description clearly states the action (list), resource (IP groups), and distinguishes from sibling `ztw_list_ip_groups` by specifying the lighter endpoint. Verb and resource are specific, making purpose immediately clear.

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?

Description explicitly compares to `ztw_list_ip_groups` and notes the lite endpoint, implying a lighter/faster alternative. However, it does not provide explicit when-not-to-use or alternative scenarios beyond that sibling.

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