zia_list_cloud_app_ssl_policy

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

The description adds minimal value beyond the existing annotations (readOnlyHint=true). It mentions 'List', which is consistent, but does not disclose additional behavioral traits such as pagination, scope, or any side effects.

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—concise but lacking detail. It is front-loaded but does not earn its place beyond stating the basic function.

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 (6 parameters, no output schema) and the presence of many sibling listing tools, the description is incomplete. It does not explain the catalog contents, filtering behavior, or return format.

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?

With low schema description coverage (17%) and 6 parameters, the description offers no explanation of the parameters (page, query, search, app_class, page_size, group_results), leaving the agent to rely solely on the schema's minimal descriptions.

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 the resource 'ZIA policy-engine cloud-application catalog (SSL Inspection)', distinguishing it from related sibling tools such as zia_list_cloud_app_policy and zia_list_ssl_inspection_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?

The description provides no guidance on when to use this tool versus alternatives (e.g., zia_list_cloud_app_policy, zia_list_ssl_inspection_rules). No when-not or exclusionary context is provided.

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