group_members

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds valuable context by stating the output is 'normalized user rows' and that 'truncated measured rather than guessed'—revealing how pagination works. This goes beyond a simple read operation description.

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 well-structured with separated Args and Returns sections, and every sentence provides meaningful detail. It is concise without unnecessary fluff, using a clear [READ] prefix and compact param explanations.

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 read-only tool with no output schema, the description provides a complete picture: it details all parameters, the return object structure, and even the truncation semantics. It lacks only error-case or permission-related context, which is not critical for this operation given its simplicity.

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?

The description includes an Args section that explicitly explains each parameter beyond the schema: group_id source ('from list_groups'), max_results definition ('Page bound (default 200)'), and target meaning ('IdP target name from config; omit for the default'). This fully compensates for the schema's lack of descriptions.

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 specifies the resource ('Members of one group') and the operation ('[READ]'), and it distinguishes this from sibling tools like list_groups, which lists groups themselves. The 'normalized user rows' detail further clarifies the output format.

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 by stating that group_id comes from list_groups, and it notes target is for a specific IdP. However, it does not explicitly state when to prefer this over alternatives (e.g., user_detail or list_users) or provide exclusion criteria, so guidance is only implicit, not explicit.

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