zia_list_cloud_app_control_actions

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

Annotations already declare readOnlyHint=true, so the description adds no new behavioral insight. No mention of pagination, rate limits, or other traits beyond the basic 'List' verb.

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?

Single sentence, 12 words, front-loads the action and resource. No wasted words; every part is meaningful.

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?

Tool is a simple list operation with 3 parameters and no output schema. Description covers the core purpose and parameter mapping. Could mention that results may be filtered via the query parameter, but annotations cover the read-only nature. Nearly complete.

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 only 33% (query has description). Description links 'category' to the required rule_type and 'cloud apps' to the optional parameter, adding context beyond schema. However, it doesn't explain possible values for rule_type or cloud_apps.

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 the action ('List') and the resource ('CAC actions for a category'), with optional cloud apps. It distinguishes from siblings like 'zia_list_cloud_app_control_rules' by specifying 'actions' vs '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?

Description implies usage context (listing actions for a category) but lacks explicit when-not-to-use or alternatives. No mention of when to prefer this over sibling tools like 'zia_list_cloud_app_policy'.

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