zia_list_ips_signature_rules

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

Adds valuable context beyond annotations: explains the tool lists custom signatures, highlights distinction from cloud firewall IPS rules, and describes pagination and client-side filtering behavior. Contradicts no 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 sentences, front-loaded with purpose and sibling distinction, no redundant information. Very efficient and well-structured.

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?

With no output schema, the description covers purpose, sibling differentiation, and pagination/filtering. Does not explicitly describe return fields, but for a list tool with clear schema examples, this is adequate.

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 100%, and description reinforces pagination (page 1-based, page_size default) and JMESPath query filtering. Adds marginal value but does not extensively detail parameter usage.

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 verb 'List', resource 'custom ZIA IPS signature rules', and includes read-only hint. Distinguishes from sibling tool zia_list_cloud_firewall_ips_rules by explaining the difference between detection signatures and enforcement rules.

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?

Explicitly distinguishes this tool from the cloud firewall IPS rule family and mentions pagination and JMESPath filtering. Could more directly state when not to use, but the sibling differentiation implies appropriate use cases.

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