zpa_get_timeout_policy_rule

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

The description only repeats the readOnlyHint annotation ('read-only'), adding no additional behavioral context such as authentication needs, error behavior, or side effects. The annotation already conveys the safety profile.

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 purpose. It is appropriately sized for the tool's simplicity.

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 simple read tool with full schema and output schema, the description is adequate but lacks guidance on deriving rule IDs and alternative sibling tools.

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?

Input schema parameters are fully described (100% coverage), so the description adds no extra meaning. The 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?

Description clearly states the action 'Get', the resource 'ZPA timeout policy rule', and the method 'by ID'. This distinguishes it from sibling tools like zpa_list_timeout_policy_rules, which list all 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 it is used when a specific rule ID is available, but it does not explicitly mention alternatives like zpa_list_timeout_policy_rules for listing all rules first. No when-not-to-use guidance is provided.

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