zia_list_ips_signature_rules

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

Annotations already declare readOnlyHint=true, so the read-only behavior is covered. The description adds no further behavioral context such as pagination, data freshness, or any side effects. For a list operation, important traits like result limits or ordering are omitted.

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 a single, direct sentence that front-loads the action and resource. It is concise, with no superfluous words. However, it could be slightly restructured to include usage hints without losing conciseness.

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 complexity of a list operation with no output schema, the description omits vital context such as available filters (beyond 'search'), pagination behavior, or how results relate to the sibling 'zia_get_ips_signature_rule'. It is incomplete for an agent to confidently invoke the 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?

The description does not mention any parameters. Schema coverage is 50% (query described in schema, search not). Since schema already documents query well, the description adds no value beyond it. For the undocumented 'search' parameter, the description offers no help. At 50% coverage, description should compensate but fails.

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 uses a specific verb 'List' and resource 'ZIA custom IPS signature rules', which distinguishes it from sibling tools like 'zia_list_rule_labels' or 'zia_get_ips_signature_rule'. The purpose is 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, filtering capabilities, or when to prefer 'zia_get_ips_signature_rule' for a single rule. Usage context is entirely implied.

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