zia_list_cloud_app_control_rules

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

Annotations already indicate readOnlyHint=true and openWorldHint=false, so the agent knows it is a safe read operation. The description adds no additional behavioral context such as authentication needs, rate limits, or what happens if the category does not exist.

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 that front-loads the verb and resource, but it is too brief and omits necessary details. While it avoids fluff, it borders on under-specification rather than 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?

For a simple list tool with two parameters and no output schema, the description lacks completeness. It does not explain the 'category' concept or how to use the query parameter. An agent would need additional information to use this tool correctly.

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 mentions 'for a category' but does not explicitly link this to the rule_type parameter. With 50% schema description coverage, the description fails to compensate for the missing parameter documentation. It does not clarify accepted values for rule_type.

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 verb (List) and resource (ZIA Cloud App Control rules) and implies scope (for a category). It distinguishes from siblings like zia_get_cloud_app_control_rule which retrieves a single rule. However, it does not explicitly explain what 'category' means or how it maps to the rule_type parameter.

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?

No guidance is provided on when to use this tool vs alternatives like zia_list_cloud_app_control_actions or zia_get_cloud_app_control_rule. There is no mention of prerequisites or context for usage.

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