List Groups

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe read operation without side effects. The description adds no behavioral context beyond what annotations provide, such as whether groups are returned in a specific order or whether pagination applies. Given the annotations cover the safety profile, a 3 is appropriate.

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 clear sentence with no wasted words. It is appropriately short for a simple list tool, front-loading the essential information.

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?

The tool is relatively simple with one required parameter awaited by annotations. The description plus schema are sufficient for an agent to call it correctly. No output schema exists, but for a list endpoint, the expected return (a list of group objects) is implied. Missing details like pagination are minor given the simplicity.

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 schema description covers 100% of parameters (course_id is clearly described as 'The Canvas course ID'). The description adds no additional parameter semantics beyond what the schema provides, but since coverage is high, a baseline of 3 is appropriate.

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 all groups in a course.' It specifies the verb (list), resource (groups), and scope (in a course). This distinguishes it from siblings like list_group_members, list_accounts, and list_courses, which operate on different resources.

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 implies usage by specifying 'in a course' and requiring course_id, but it does not explicitly state when to use this versus alternatives, nor does it mention any limitations or alternative tools. For a simple list operation, this is adequate but leaves some room for improvement in guidance.

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