zia_list_ssl_inspection_rules

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

The description does not add any behavioral traits beyond the annotations (readOnlyHint=true). It does not disclose pagination, rate limits, or whether the tool returns all rules at once. With annotations already indicating a safe read, the description adds minimal value.

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 very concise (5 words) but lacks structure and front-loading of critical information. It is not verbose, but it is under-specified, earning a middle score.

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 tool's simplicity (list rules, one optional param, no output schema), the description is barely adequate. It does not explain how to use the query parameter, what the output looks like, or any context about the rules. More details would be helpful.

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 input schema has one optional parameter (query) with a detailed description, covering 100% of parameters. The tool description does not mention this parameter, so it adds no extra meaning beyond the schema. Baseline is 3.

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 'List ZIA SSL Inspection rules' clearly states a specific verb (list) and resource (SSL Inspection rules), and it differentiates from the sibling 'zia_get_ssl_inspection_rule' which retrieves a single rule. However, it lacks any additional scope or context.

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 versus alternatives, such as zia_get_ssl_inspection_rule for a specific rule, or any prerequisites. The description is purely a restatement of the tool's name.

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