zpa_get_timeout_policy_rule

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

The annotation 'readOnlyHint: true' already discloses the read-only nature, and the description merely repeats 'read-only' without adding any extra behavioral context (e.g., return format, pagination, rate limits). It adds no value beyond the annotations.

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 key information ('Get one ZPA timeout policy rule') and adds '(read-only)' as a secondary note. There is no redundant or irrelevant content.

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?

The tool is a simple get-by-ID operation with one required and one optional parameter, and no output schema. The description is adequate for basic usage but omits context such as how to obtain the rule ID (e.g., from the list tool) or the meaning of microtenant_id, leaving some gaps for an 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?

Schema description coverage is 0%, so the description must compensate for parameter meaning, but it does not mention 'rule_id' or 'microtenant_id' at all. The parameter names are somewhat self-explanatory, but the description provides no additional context such as required formats or relationships.

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 action 'Get' and the resource 'one ZPA timeout policy rule', distinguishing it from the sibling tool 'zpa_list_timeout_policy_rules' by specifying a single object. It is specific and unambiguous.

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 the tool is for fetching a particular rule by ID, given the required 'rule_id' parameter and the existence of a list sibling. However, it does not explicitly state when to use it versus alternatives or provide exclusions, so it lacks explicit guidance.

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