zia_list_static_ips

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

Annotations already declare readOnlyHint=true, which is reinforced by the description's 'read-only' claim. The description adds value by mentioning JMESPath client-side filtering support, which is a behavioral trait not covered by annotations. No contradictions.

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 (two sentences) and front-loaded with the core purpose. Every sentence provides useful information with no redundancy or fluff.

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 presence of an output schema and full schema coverage, the description is adequate for a simple read-only list tool. It covers the purpose and filtering capability. However, it lacks details on prerequisites or error scenarios, which could be helpful but are not critical for this low-complexity tool.

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 100%, so baseline is 3. The description's mention of JMESPath filtering largely mirrors the schema's description of the 'query' parameter. It does not add significant new meaning beyond what is already in the schema.

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 ZIA static IPs (read-only)', using a specific verb and resource. It distinguishes from the sibling tool 'zia_get_static_ip' (which retrieves a single IP) by nature of 'list' vs 'get'. The additional mention of JMESPath filtering further clarifies the tool's capability.

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 for retrieving a list of static IPs and supports client-side filtering via JMESPath, but it does not explicitly state when to use this tool over alternatives like 'zia_get_static_ip' or provide any exclusion criteria. The guidance is minimal.

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