List course classmates

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds a valuable behavioral detail beyond annotations: 'If the course hides the roster, returns a note instead of an error.' This informs the agent that a non-error response may still indicate unavailability, which is useful for interpretation.

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?

Two concise sentences with no superfluous information. The core purpose is stated first, followed by a key behavioral exception. Every word earns its place.

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 simple one-parameter tool with no output schema and safety annotations covering read-only behavior, the description provides the essential purpose and a notable edge case. It does not describe the return format or fields, but given the tool's simplicity, that is not a critical gap. It is complete enough for an agent to call it correctly.

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?

Schema coverage is 100% with a single parameter, courseId, described as 'Canvas course id.' The tool description adds no additional parameter meaning beyond this. Since the schema already documents the parameter adequately, the baseline of 3 applies.

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 student roster for a course,' which clearly identifies the resource and scope. It does not explicitly include a verb like 'list,' but the title provides that, and the meaning is unambiguous. It distinguishes from siblings like canvas_list_group_members by focusing on the course roster, though it doesn't name alternatives.

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 gives no guidance on when to use this tool versus alternatives such as canvas_list_group_members or canvas_list_courses. It only implies use for retrieving the roster, but there is no explicit context, prerequisites, or exclusion criteria. The added behavior about hidden rosters is behavioral, not usage guidance.

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