canvas_list_assignments

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds concrete behavioral context: 'All requests use Canvas GET endpoints; this server cannot modify Canvas.' This goes beyond the annotation hints and clarifies the exact HTTP method.

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 compact and front-loaded with the read-only nature. However, the first sentence ('Read-only Canvas LMS access.') is mostly redundant with the annotation, and the second sentence restates 'cannot modify Canvas.' Overall, it is concise but not maximally efficient.

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?

With no output schema and three parameters, the description should explain return values and parameter effects. It only covers the overall purpose. Missing details about pagination (limit), filtering (bucket), and course_id scope make it incomplete for an agent to invoke effectively.

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%, and the description gives no explanation of the parameters (limit, bucket, course_id). With three optional parameters, the description should compensate by explaining their semantics, but it only mentions 'one course or all active courses,' which is insufficient.

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 a specific verb and resource: 'List assignments for one course or all active courses.' This clearly distinguishes it from siblings like canvas_get_assignment (single assignment) and canvas_list_courses (lists courses).

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 by stating the tool lists assignments, and the scope 'for one course or all active courses' provides context. However, it does not explicitly mention alternatives or when not to use it, leaving room for ambiguity.

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