zia_get_ssl_inspection_rule

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

The annotations already indicate read-only and non-open-world behavior. The description adds a behavioral note about 'member references' in the response, which provides additional context about the data returned. This is a meaningful addition beyond the annotations, though not exhaustive.

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, concise sentence that immediately states the action and object. There is no unnecessary information, and it is well-structured for quick understanding.

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 operation with a single ID parameter and no output schema, the description is sufficient to convey the tool's purpose. The mention of 'member references' hints at the response content, which adds a bit of context without overcomplicating the description.

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 only parameter, rule_id, has no description in the schema, and the tool description merely states 'by ID' without elaborating on its format, constraints, or meaning. The description does not add value beyond what the parameter name implies, so the parameter semantics are under-specified.

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 tool's function: it retrieves a single SSL Inspection rule by its ID. The verb 'Get' is specific, and the mention of 'single' and 'by ID' distinguishes it from the list operation, making its purpose unambiguous.

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 implicitly conveys when to use this tool: when you have a specific rule ID and need that particular rule, as opposed to listing all rules. While it doesn't explicitly state alternatives or conditions, the context is clear enough for an agent to infer the appropriate usage.

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