zpa_get_app_protection_rule

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

The description echoes the annotation readOnlyHint=true by stating 'read-only,' adding minimal extra context. It also clarifies the rule type as 'inspection,' which is helpful. However, it does not disclose other behaviors like idempotency, error handling, or required permissions beyond what annotations provide.

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 concise at one sentence, front-loading key information. However, it omits important details about parameters, making it less effective.

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 get tool with annotations, the description is minimally adequate but fails to cover expected parameters, return values, or error conditions. Given the 0% schema coverage, more detail is needed to ensure the agent can invoke the tool correctly.

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%, meaning the schema provides no parameter descriptions. The description also lacks any explanation of the parameters rule_id and microtenant_id, leaving the agent with only names and types. This severely hampers correct usage.

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 'Get one ZPA app-protection (inspection) policy rule (read-only).' It specifies the action (Get) and resource (app-protection policy rule) with scope (one), and implicitly distinguishes from sibling 'zpa_list_app_protection_rules' by indicating a single item retrieval.

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 provides no explicit guidance on when to use this tool versus alternatives, such as when to use 'zpa_list_app_protection_rules' for listing. The usage is implied by the name ('get' versus 'list'), but no direct comparison or prerequisites are stated.

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