Group Members

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, repeatable read operation. The description adds useful context about filtering by search term and returning access levels, but doesn't disclose pagination behavior, rate limits, authentication requirements, or what happens with invalid group paths. With annotations covering the safety profile, this is adequate but not rich.

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, efficient sentence that front-loads the core purpose ('List group members with access levels') and includes the key optional feature ('optionally filtered by search term'). There's zero waste or redundancy.

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 that annotations cover safety (read-only, idempotent, non-destructive), schema coverage is 100%, and this is a straightforward list/query operation, the description is reasonably complete. However, without an output schema, the description could better explain the return format (e.g., paginated list with access levels). The mention of 'access levels' is helpful but could be more explicit about the response structure.

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 100%, so all parameters are well-documented in the schema itself. The description mentions 'optionally filtered by search term' which aligns with the 'search' parameter, but doesn't add meaningful semantics beyond what the schema provides. The baseline of 3 is appropriate when the schema does the heavy lifting.

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's purpose: 'List group members with access levels' - a specific verb+resource combination. It distinguishes from some siblings like 'search_users' or 'get_current_user' by focusing on group membership, but doesn't explicitly differentiate from potential similar tools that might also list group members.

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 provides implied usage context through 'optionally filtered by search term' and the required 'groupPath' parameter, suggesting this is for exploring specific groups. However, it doesn't explicitly state when to use this versus alternatives like 'search_users' or 'get_group_projects', nor does it mention prerequisites or exclusions.

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