List my groups

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

Annotations already declare readOnlyHint: true, openWorldHint: true, idempotentHint: true, and destructiveHint: false, so the description doesn't need to restate safety. It adds the behavioral detail that the result is a combination of course project groups and community groups, which goes beyond annotations and helps the agent understand the scope of results. However, it doesn't mention potential pagination or ordering, which is a reasonable gap for a simple list tool.

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?

A single sentence that is both informative and succinct. It front-loads the core purpose and includes the defining nuance (types of groups) without any filler.

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 tool with no parameters and no output schema, the description is sufficient. It tells the agent exactly what will be returned (a list of groups they belong to) and clarifies the group types. Since it's a simple list endpoint, no additional documentation like pagination details or response format is strictly necessary, though slightly more output detail could be added.

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 has zero parameters, so the description doesn't need to explain any. Baseline for 0 params is 4, and the description doesn't lack anything here.

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 states the specific verb 'list' and the resource 'groups' with a clear scope 'all groups you belong to'. It further specifies 'course project groups + community', which distinguishes it from other group-related tools like canvas_get_group (retrieves a single group) and canvas_list_group_members (lists members of a group).

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 clearly implies when to use it: when you need all groups the current user belongs to. It doesn't explicitly exclude alternatives, but the sibling tools for fetching a specific group or listing group members are obviously different. It provides useful context by naming the group categories.

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