zms_list_nonces

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

The description discloses the output structure ('Returns one row per nonce (eyez_id, name, status, expiry)') and reiterates read-only behavior, which aligns with the readOnlyHint annotation. It also mentions a prerequisite (ZSCALER_CUSTOMER_ID). However, it does not disclose other behaviors like pagination limits, error handling, or rate limits. Given annotations already cover safety, this adds some transparency but not comprehensive.

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, consisting of a single primary sentence and a short additional note. It is front-loaded with the main purpose, and every sentence adds value. No fluff or redundancy.

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 is incomplete for a tool with 6 undocumented parameters. It does not explain how pagination, sorting, query, search, or page_size work, nor does it provide examples or clarify the output format beyond listing field names. Without additional context, a user cannot effectively invoke this tool with appropriate parameters. The description fails to compensate for the schema's lack of parameter explanations.

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 input schema includes 6 parameters (page, sort, query, search, sort_dir, page_size) with no descriptions, and the tool description does not explain any of them. The only mention is 'Requires ZSCALER_CUSTOMER_ID' which is not a parameter. The description adds zero meaning to the parameters, leaving the user to guess their purpose.

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's purpose: 'List ZMS enrollment nonces.' It uses a specific verb ('List') and a resource ('ZMS enrollment nonces'), distinguishing it from the sibling tool `zms_get_nonce` which likely retrieves a single nonce. The purpose is unambiguous.

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 does not provide guidance on when to use this tool versus alternatives. It mentions a requirement ('Requires ZSCALER_CUSTOMER_ID') but does not explain scenarios, alternatives, or when to prefer this over `zms_get_nonce` or other list tools. The usage context is minimal.

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