zms_list_default_policy_rules

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

The description adds value beyond the readOnlyHint annotation by explaining that the tool lists the default rules that are evaluated when no custom rule matches. This clarifies the role of the data. 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?

The description is three concise sentences with no fluff. It front-loads the purpose, followed by read-only note, then additional context. Could be slightly more structured but is efficient.

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 description explains the purpose and context of default rules, but lacks detail on pagination, error handling, or result structure. Given no output schema, more context about the return format would be helpful. Adequate but not comprehensive.

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 only 33% (only query parameter has a description), yet the tool description does not mention any of the parameters (query, page_num, page_size). It fails to add meaning or guidance about how to use pagination or filtering.

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 it lists 'ZMS default policy rules' and explains they are 'built-in default rules evaluated when no custom rule matches,' which is specific and distinguishes it from sibling tools like zms_list_policy_rules that handle custom 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 notes it is read-only and requires ZSCALER_CUSTOMER_ID, but does not explicitly state when to use this tool versus alternatives or when not to use it. The context implies it's for inspecting defaults, but guidance is indirect.

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