list_students

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

With no annotations provided, the description carries the full burden. It does disclose output scope (students only, with email and enrollment details) and implies a read-only listing, but it does not mention pagination sensitivity, enrollment status filters, or that 'all students' may require multiple pages.

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, focused sentence with no filler. The verb and resource are front-loaded, and the included fields add useful value without bloat.

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 description is adequate for a simple listing tool: the required course_id is clear and return fields are partially described. However, with no output schema and no mention of pagination behavior or selection among similar sibling tools, an agent might not know how to fully retrieve all students or choose this over list_enrollments.

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 already documents both course_id and per_page with 100% coverage, so the baseline is 3. The description adds no additional meaning beyond what the schema provides, such as how per_page interacts with the 'all students' claim.

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 lists students in a specific Canvas course and names the included fields (email, enrollment details). This distinguishes it from course-level tools like list_courses and list_assignments, though it does not explicitly differentiate from closely related siblings like list_course_users or list_enrollments.

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?

No guidance is provided about when to use list_students versus list_course_users, list_enrollments, or get_user_enrollments. The description implies the intended context, but it does not state exclusions or alternatives.

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