zdx_list_application_users

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

Annotations already declare readOnlyHint=true, so the description's read-only note is redundant but consistent. The description adds the JMESPath filtering behavior, which is useful. However, it does not disclose pagination, rate limits, or data freshness (e.g., the 'since' parameter defaults to 2h).

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 (one sentence with a second clause) and front-loads the purpose. No wasted words, but could include a hint about the required app_id parameter (though it's in the schema) and potential time default.

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's complexity (8 parameters, output schema, time sensitivity via 'since' parameter), the description lacks context such as the time-window nature of the data, who the users are, and any required permissions. The presence of an output schema mitigates return structure knowledge, but the description is insufficient for a complete understanding.

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 coverage is 100% with detailed descriptions for all 8 parameters, including the JMESPath query. The description does not add new parameter semantics beyond what the schema already provides, meeting the baseline expectation.

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 lists users for a ZDX application and is read-only, aligning with its name. It adds the JMESPath filtering capability, but does not explicitly differentiate from similar tools like zdx_get_application_user (single user) or zdx_list_applications.

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 guidance on when to use this tool versus alternatives (e.g., zdx_get_application_user for a single user). Does not specify prerequisites or context such as requiring prior app_id retrieval.

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