List assignments

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

Annotations already establish that this is a read-only, non-destructive operation. The description adds only that results include due dates and submission status, but does not explain pagination, ordering, permission scope, or how the bucket filter changes results.

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 front-loaded sentence with no wasted wording. It is appropriately sized for a simple listing tool, though brevity contributes to the missing usage and parameter detail.

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 read-only list tool with annotations and a mostly self-explanatory schema, the description is still incomplete. It omits the important bucket filtering behavior and any guidance on how this differs from getting a single assignment, leaving the agent to infer usage from the schema.

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 50%: the bucket parameter is described in the schema, while course_id has no description there. The tool description does not mention either parameter or clarify what the bucket values mean or how omission behaves, so it does not compensate for the coverage gap.

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 identifies the resource and scope: assignments in a specific course, including due dates and submission status. It does not explicitly state a verb or distinguish itself from sibling tools like canvas_get_assignment or canvas_list_planner_items, but the purpose is clear.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention canvas_get_assignment for a single assignment or canvas_list_planner_items for cross-course planning, nor does it explain when the bucket filters are appropriate.

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