canvas_group_members

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns member names, profile information, and contact details (if shared), which adds behavioral context beyond a basic list operation. However, it does not mention potential limitations like permissions required, rate limits, or error conditions, leaving gaps in transparency for a read operation.

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 appropriately sized and front-loaded, starting with the core purpose ('List members of a specific group.') followed by return details and usage guidance. Each sentence adds value, with no wasted words. However, it could be slightly more structured (e.g., separating return values into a bulleted list in the text), but overall it is efficient.

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's low complexity (1 parameter, read-only operation) and no output schema, the description provides a basic overview of purpose and returns, which is adequate. However, it lacks details on output format (e.g., structure of returned data), error handling, or dependencies, making it incomplete for full agent understanding without additional context.

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 input schema has 100% description coverage, with 'group_id' clearly documented as 'The group ID.' The description does not add any parameter semantics beyond this, as it focuses on the tool's purpose and output. With high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 members of a specific group.' It uses a specific verb ('List') and resource ('members of a specific group'), making the action and target explicit. However, it does not explicitly differentiate from sibling tools like 'canvas_group_list' (which likely lists groups rather than members), so it misses full sibling distinction.

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 guidance: 'Use to see who is in your group for collaboration.' This suggests a context of group collaboration, but it does not explicitly state when to use this tool versus alternatives (e.g., 'canvas_group_list' for listing groups) or any exclusions. The guidance is helpful but lacks specificity about tool selection.

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