zid_get_group_users

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

The description explicitly states 'Read-only', matching the readOnlyHint=true annotation, and adds detail on the return content (id, login name, display name, primary email). This goes beyond the annotation to inform the agent about the data returned.

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 extremely concise: three sentences that together convey purpose, safety, and output format without any extraneous information. Every sentence earns its place.

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 4 parameters, no output schema, and the context of many sibling tools, the description covers the core functionality and return fields but omits details on pagination (limit/offset), client-side filtering (query), and differentiation from the by-name variant. Some gaps remain for an agent to use it confidently without further exploration.

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?

With only 25% schema description coverage, the description does not compensate for the undocumented parameters (limit, offset, query). While it implies the use of group_id ('by group ID'), it fails to explain how limit and offset control pagination or how query works for client-side filtering. This leaves significant gaps for proper invocation.

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 action ('list'), the resource ('users that belong to a ZIdentity group'), and the method ('by group ID'). It also specifies the output format ('lean user summaries' with listed fields), distinguishing it clearly from sibling tools like zid_get_group (which gets group details) or zid_search_users (which searches users).

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 implies usage when you need to list group members by group ID, but it does not provide explicit guidance on alternatives like zid_get_group_users_by_name or when to use one over the other. No exclusions or prerequisites are stated.

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