get_zia_users

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'read-only'. It adds the list-vs-by-ID behavioral distinction but does not disclose pagination behavior, result shape, or what happens when no filters are supplied. With annotations covering the safety profile, this is acceptable but thin.

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 a single front-loaded sentence that immediately identifies the resource and operation. Every word earns its place; 'read-only' is slightly redundant with the annotation but not harmful.

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?

With 7 optional parameters, no output schema, and a large sibling tool set, a one-sentence description is insufficient. It does not explain return values, pagination, filter combinations, or the distinction between list and by-ID behavior beyond the bare minimum. The query parameter's rich guidance lives only in the schema, not the description.

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 description coverage is only 14%, so the description needed to compensate, but it only generically says 'optional filters' and 'fetch one by ID'. It does not explain dept, name, group, page, page_size, or how user_id relates to the other parameters. Only the query parameter has meaningful schema documentation.

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 uses a specific verb ('Read') and resource ('ZIA users'), and clearly distinguishes the two modes: list with optional filters or fetch one by ID. This is enough to separate it from sibling user-related tools like zid_get_user or get_zia_user_departments.

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 clearly states when to use the tool: for listing ZIA users with optional filters or fetching a single user by ID. It does not explicitly name alternatives or exclusions relative to sibling tools, but the context is clear enough for a simple read operation.

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