zia_get_ips_signature_rule

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

Annotations already declare 'readOnlyHint=true' indicating a safe read operation, which is consistent with the description. The description adds no extra behavioral traits beyond the annotation, but the annotation itself provides sufficient safety context. The phrase 'with its body' is vague but does not contradict anything.

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 sentence of 13 words, directly stating the tool's function. It is front-loaded and contains no unnecessary information.

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?

For a simple get-by-ID tool with one parameter and no output schema, the description covers the basic purpose. However, it does not explain the return format or what 'body' means, leaving some ambiguity. It is adequate but not comprehensive.

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 0%, so the description must compensate. It mentions 'by ID', which matches the parameter name 'rule_id', but provides no additional details such as format, example, or expectations. The description adds minimal value beyond what the parameter name already conveys.

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 action 'Get', the resource 'a single ZIA custom IPS signature rule', and the method 'by ID with its body'. The word 'single' implies a distinction from the sibling tool 'zia_list_ips_signature_rules' which retrieves all rules, but it does not explicitly differentiate from other siblings.

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 compared to alternatives, such as listing tools like 'zia_list_ips_signature_rules', or any prerequisites. The usage context is only implied by the tool name and description, but not explicitly stated.

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