zms_get_nonce

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

Annotations provide readOnlyHint=true; description reinforces 'Read-only.' Additionally, it discloses data sensitivity ('payload may carry sensitive enrollment data — handle accordingly') and authentication requirement ('Requires ZSCALER_CUSTOMER_ID'), which are beyond 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 sentences, each adding value: clear action, key parameter, security context, and requirement. No redundant or irrelevant information. Front-loaded with the core purpose.

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 simple get operation with one required parameter and an existing output schema, the description covers input, authentication, sensitivity, and read-only nature. No missing critical information given the available structured data.

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?

Input schema has 0% description coverage; description adds that the tool is 'Keyed by eyez_id,' confirming the parameter's role. However, it does not explain the format, source, or semantics of eyez_id beyond being a key. Baseline 3 because minimal additional meaning.

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?

Description clearly states 'Get one ZMS nonce' with verb ('Get') and resource ('ZMS nonce'). It adds context: read-only, keyed by eyez_id, sensitive data, and authentication requirement. Distinguishes from siblings as it is a unique tool among many Zscaler product tools.

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?

No explicit guidance on when to use this tool versus alternatives. It implies usage for fetching a single nonce but does not mention scenarios or exclusions. The tool is unique among siblings, reducing competition, but usage context is not provided.

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