zpa_get_isolation_policy_rule

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

Annotations already declare readOnlyHint=true, so the description reinforces that. However, it does not disclose any additional behaviors like error handling or permissions. Since annotations cover the safety profile, the description adds minimal context.

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 with no waste. However, for a tool with 0% schema coverage and two parameters, it is too brief. While concise, it lacks necessary detail, making it less useful.

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?

No output schema exists, yet the description does not explain what the tool returns (e.g., the rule data). It also does not mention that a prior list operation is needed to obtain the rule_id. Overall incomplete for a getter without return info.

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 description coverage is 0%, meaning parameters have no descriptions. The tool description does not explain any parameters; it only mentions 'one' rule. The agent gets no guidance on 'rule_id' or 'microtenant_id' beyond the schema.

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 retrieves a single ZPA isolation policy rule and is read-only. The verb 'Get' and resource 'isolation policy rule' are specific. It distinguishes from sibling list tools like 'zpa_list_isolation_policy_rules' and other getters.

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?

Usage is implied: use this tool to get a specific rule by ID versus listing all rules. However, no explicit guidance on when not to use it, prerequisites (e.g., needing to list first), or alternatives.

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