zpa_list_app_protection_rules

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

The read-only behavior is already declared in annotations (readOnlyHint=true); the description merely restates it. No additional traits like pagination, rate limits, or result size are disclosed.

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 very concise and front-loaded, with only essential information. However, it could include more details without harming brevity.

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?

Given no output schema, the description should cover return format or pagination, but it does not. The microtenant_id parameter is also left unexplained, leaving gaps for the 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?

The schema has two parameters (query and microtenant_id) with 50% description coverage. The description does not explain the microtenant_id parameter or add any meaning beyond the schema's query description.

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 tool lists ZPA app-protection policy rules and explicitly marks it as read-only. It distinguishes from sibling tools like 'zpa_list_access_policy_rules' by specifying 'app-protection'.

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 identifies the tool as read-only, which implies safe usage, but provides no guidance on when to use this tool vs alternatives or any prerequisites.

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