list_assignments

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

The readOnlyHint annotation already indicates this is a read operation. The description adds no further behavioral context such as pagination, ordering, or filtering beyond the required course identifier.

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 extremely concise with two lines, no unnecessary words, and uses code formatting for parameters. Every part is purposeful.

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?

While the output schema is present, the description lacks details on return format, pagination, or how this differs from similarly named sibling tools like list_submissions. It is minimally complete for a simple list operation.

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 parameter has 0% description coverage, but the description explains that course_identifier is a 'Course code or Canvas ID', adding meaning beyond the raw anyOf type. This compensates for the schema 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 states 'List assignments for a specific course', specifying the verb (list), resource (assignments), and scope (course). This distinguishes it from siblings like get_assignment_details or create_assignment.

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 for listing assignments but does not explicitly guide when to use this tool versus alternatives like get_assignment_details for a single assignment or list_submissions for submissions.

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