zpa_list_isolation_policy_rules

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

The description adds no behavioral traits beyond the annotation readOnlyHint: true. It does not disclose any other effects, auth needs, rate limits, or output format. With annotations already covering read-only, the description provides no additional 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 a single short sentence, which is concise but too brief for a tool with two parameters and sibling listers. It is front-loaded with the purpose, but misses important details, making it minimally viable.

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 that there is no output schema, the description should explain the return value, pagination, or filtering capabilities. It only states what the tool does and that it's read-only. The undocumented microtenant_id parameter is not addressed, leaving gaps for the agent.

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 description adds no meaning beyond the input schema. The schema covers the query parameter with a detailed description, but microtenant_id is undocumented. The description does not mention either parameter, so it fails to compensate for the 50% schema coverage gap.

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 'List ZPA isolation policy rules' with a verb and resource, and adds '(read-only)' for extra clarity. It distinguishes from sibling tools like zpa_get_isolation_policy_rule (single rule) and other policy rule listers, but does not explicitly differentiate from them.

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 on when to use this tool versus alternatives. No mention of when to use list vs get, or how it compares to other policy rule listers (e.g., zpa_list_access_policy_rules). The description only says it's read-only.

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