canvas_list_assignments

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'List assignments' and does not mention pagination, sorting, authentication, read-only guarantees, or output format. This is not misleading, but it adds almost no behavioral context beyond the tool's name.

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 one short sentence with no filler, and the key scope is front-loaded. While it is minimal, the length is appropriate for a simple listing tool and every word contributes to meaning.

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 a simple list operation with one required parameter, so the description covers the core call adequately. However, with no annotations and no output schema, it omits return-format details and any edge-case behavior, leaving some contextual gaps for the agent.

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 description coverage is 0%, so the description must compensate. The phrase 'for one Canvas course' clarifies that course_id identifies a single course, adding a bit of meaning beyond the raw schema. However, it does not name the parameter or explain its expected format or constraints beyond what the schema already shows.

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 verb 'List', the resource 'assignments', and the scope 'one Canvas course'. This clearly distinguishes it from siblings like canvas_list_courses, which list courses. It does not explicitly reference the alternatives, so it stops short of a 5.

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 canvas_list_courses or canvas_get_upcoming. The only hint is the phrase 'List assignments', which implies its use but does not provide any exclusions, prerequisites, or alternative routing.

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