zpa_list_timeout_policy_rules

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

The description merely repeats the 'read-only' hint already present in annotations, adding no new behavioral context. No mention of pagination, limits, or side effects. With annotations already declaring readOnlyHint=true, the description should provide additional behavioral insights but fails to do so.

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 extremely concise (one short phrase) and front-loaded, but it is too minimal to be considered well-structured. It lacks sufficient detail to earn its place given the available space.

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?

For a list tool with 2 parameters, no output schema, and many siblings, the description is grossly incomplete. It does not explain what timeout policy rules are, how to interpret the results, or how to filter effectively. The minimal description fails to provide a complete understanding.

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 50%, but the description does not mention or explain any parameters. The 'query' parameter has a detailed schema description, but 'microtenant_id' has none, and the description adds no value. For low coverage, description must compensate; it does not.

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 'list' and the resource 'ZPA timeout policy rules', and includes the qualifier 'read-only'. This distinguishes it from the sibling tool 'zpa_get_timeout_policy_rule' which retrieves 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?

No guidance is provided on when to use this tool versus alternatives, such as when to use the 'get' variant or other list tools. The description lacks any contextual hints about prerequisites or typical use cases.

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