zms_list_default_policy_rules

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

The description confirms read-only behavior, matching the readOnlyHint annotation, and adds useful context such as the default-rule evaluation semantics and the requirement for ZSCALER_CUSTOMER_ID. It does not discuss pagination or output shape, but the annotation already covers the safety profile.

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 short and front-loaded, using three compact sentences to state the action, the safety/read-only nature, the default-rule context, and an environment requirement. Every sentence earns its place.

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 straightforward read-only list tool, this description covers the core concepts: what is listed, how the default rules fit into rule evaluation, and a required environment value. It lacks output-format notes, but no output schema is provided and the tool is simple enough that the remaining gaps are minor.

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 description itself adds no parameter-level semantics. Schema description coverage is only 33%; the query parameter is well documented in the schema, but page_num and page_size are effectively unexplained, and the description does not compensate for this low parameter coverage.

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 opens with a clear verb and resource: 'List ZMS default policy rules.' It further clarifies scope by explaining these are the built-in default rules evaluated when no custom rule matches, which distinguishes this tool from the sibling zms_list_policy_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 gives clear when-to-use context: this lists the hardcoded defaults that apply only when no custom rule matches. It does not explicitly name an alternative such as zms_list_policy_rules, so it stops short of fully explicit when-to-use versus when-not-to-use guidance.

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