zpa_get_isolation_policy_rule

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

Annotations already declare readOnlyHint=true, and the description confirms 'read-only'. No additional behavioral traits are disclosed, such as permissions or rate limits. With annotations present, the description adds minimal extra transparency.

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 front-loads the core purpose. Every word is necessary and there is no fluff.

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?

The description covers the essential action and resource. Given the output schema exists for return values, the description does not need to detail them. It is complete for a simple read-only getter, though it could mention that it retrieves a single rule.

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 100%, and the description adds no extra meaning beyond saying 'by ID' which aligns with the required 'rule_id' parameter. No elaboration on 'microtenant_id' or 'service'. Baseline score of 3 is appropriate.

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 'Get', the resource 'ZPA isolation policy rule', and the qualifier 'by ID'. It also includes 'read-only' for clarity. This distinguishes it from list tools like 'zpa_list_isolation_policy_rules' and other policy rule 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?

The description implies usage when you have a specific rule_id, but it does not explicitly state when not to use this tool or mention alternatives. However, the context signals and sibling list provide enough differentiation for an AI agent.

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