list_members

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it only states the basic function. It fails to mention that this is a read-only operation, any pagination behavior (though page_size parameter exists), rate limits, or error handling for invalid group_ids. The transparency is insufficient.

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 at one short sentence. While it avoids redundancy, it could benefit from a bit more context without becoming verbose. It is front-loaded but slightly under-specified for a tool with no annotations.

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 lack of annotations and output schema, the description is incomplete. It does not explain return format, pagination behavior, or any side effects. For a simple list operation, users need minimally to know about pagination and potential empty results, which are absent.

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 tool description adds no additional meaning beyond the input schema, which already has 100% coverage with descriptions for all three parameters. Per calibration guidelines, high schema coverage warrants a baseline of 3. The description does not enhance parameter understanding.

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') and the resource ('members of a Google Chat space or DM'). It effectively distinguishes from siblings like 'list_spaces' (lists spaces) and 'list_space_files' (lists files). The verb+resource combination is specific and unambiguous.

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 no explicit guidance on when to use this tool versus alternatives (e.g., for listing spaces vs members). It only implicitly suggests that group_id comes from list_spaces via the schema description, but no proactive direction on prerequisites or exclusion scenarios is given.

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