tc_list_group_users

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that project_id resolves the region and outlines the return structure, which goes beyond annotations and clarifies behavior. No contradiction.

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 compact and well-structured with Args and Returns sections; every sentence provides necessary information without fluff.

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 list tool with two parameters and an output schema, the description covers purpose, parameter semantics, and return format. It omits pagination or error details, but given the simplicity and annotation coverage, it is adequate.

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 0% schema coverage, the description compensates by defining both parameters: project_id as 'Project ID (resolves the region)' and group_id as 'Group ID from tc_list_groups'. This gives meaningful context beyond the raw schema's generic string types.

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 'List the members of a project group' with a specific verb and resource, distinguishing it from sibling tools like tc_list_groups (lists groups) and tc_list_project_members (lists project 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?

It provides a prerequisite by noting group_id comes from tc_list_groups, and explains that project_id resolves the region. However, it does not explicitly contrast with alternative tools like tc_list_project_members, so it doesn't fully guide when-not-to-use.

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