zpa_list_timeout_policy_rules

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

The description's '(read-only)' only restates the readOnlyHint=true annotation and adds no new behavioral context such as pagination behavior, result size limits, scoping, or tenant specifics. There is no contradiction with annotations, but no additional disclosure beyond them.

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?

One short, front-loaded sentence with no filler. The resource and operation are immediately clear, and every word carries meaning.

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?

Minimally viable for a simple read-only list tool: operation and resource are clear, and the query parameter has a thorough schema description. However, it lacks guidance on pagination, return shape, and the semantics of the other four parameters, leaving clear gaps.

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 only 20%, with just the query parameter documented. The description does not explain page, page_size, search, or microtenant_id, so it fails to compensate for the low schema coverage.

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?

Description uses the specific verb 'List' and names the exact resource 'ZPA timeout policy rules'; '(read-only)' clarifies non-mutating intent. This clearly distinguishes it from the sibling zpa_get_timeout_policy_rule, which fetches a single rule.

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 verb 'List' and plural resource imply this is for retrieving a collection, but there is no explicit guidance about when to use it versus zpa_get_timeout_policy_rule or other policy list tools. No exclusions or alternative recommendations are provided.

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