zms_list_policy_rules

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

Declares read-only behavior (matching annotations) and describes return fields, pagination details, and the fetch_all caveat. No contradictions with 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?

Three concise, front-loaded sentences with no wasted words, efficiently covering purpose, behavior, and constraints.

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?

Discloses return fields, pagination, and the required ZSCALER_CUSTOMER_ID, but could elaborate on prerequisites or output format further given the absence of an output schema.

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?

Adds meaning for 'fetch_all' (bypass pagination, use sparingly) and mentions name/action filters, but 5 of 6 parameters (except query) lack description in the schema or 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?

Clearly states 'List ZMS microsegmentation policy rules' with a specific verb and resource, distinguishing it from numerous sibling tools that deal with different Zscaler products (ZIA, ZPA, etc.).

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?

Implied usage through 'Read-only' and filter hints, but no explicit guidance on when to use this tool over alternatives like zia_list_url_filtering_rules or zpa_list_access_policy_rules.

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