zpa_get_access_policy_rule

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

The description echoes the readOnlyHint annotation with 'read-only', adding no additional behavioral context beyond what annotations already provide. No disclosure of rate limits, authentication, or other traits.

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, front-loaded sentence with no redundant or extra words. Every word serves a purpose.

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 and the presence of an output schema, the description adequately covers the core functionality. However, it could mention that rule_id is required or provide more context about the response.

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%, so baseline is 3. The description does not add any parameter-specific information beyond what is already in the schema, such as clarifying the role of microtenant_id or service.

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 access policy rule', and the method 'by ID', along with the read-only nature. It effectively distinguishes from sibling tools like zpa_list_access_policy_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 implies usage when you have a specific rule ID, but does not explicitly mention when to use this tool versus alternatives like the list tool. No exclusions or context provided beyond the basic purpose.

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