zms_list_nonces

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

Annotations already provide readOnlyHint=true, and the description reinforces 'Read-only'. Beyond annotations, it adds useful behavioral details: returns one row per nonce with specific fields and requires a header. This gives the agent a clear picture of what the tool does and what is needed.

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 very concise: three short sentences that front-load the action ('List ZMS enrollment nonces') and add essential context without redundancy. Every sentence adds value.

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?

Given the tool has 6 parameters and no output schema, the description is insufficient. It omits details on pagination, filtering, and sorting behaviors, and does not cover error conditions or rate limits. The agent lacks enough context to use the tool effectively beyond a simple call.

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?

Only the 'query' parameter has a schema description (low coverage of 17%). The tool description does not explain the other five parameters (page, sort, search, sort_dir, page_size), leaving the agent to guess how pagination, sorting, and searching work. The description should have elaborated on these to compensate for the sparse schema.

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 'List ZMS enrollment nonces' with a specific verb and resource, and further specifies it's read-only and returns fields (eyez_id, name, status, expiry). It distinguishes from the sibling 'zms_get_nonce' by implying a list operation vs. a single get.

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 mentions 'Requires ZSCALER_CUSTOMER_ID' as a prerequisite, but provides no explicit guidance on when to use this tool versus alternatives like 'zms_get_nonce'. The context is clear enough to infer, but exclusions or when-not-to-use are missing.

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