Canvas MCP Server

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

No annotations are provided, so the description carries full burden. It states the action ('List submissions') but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires specific permissions, what the output format includes (e.g., pagination, filtering options), or any rate limits. The description is minimal and lacks essential context for safe invocation.

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 appropriately concise with two sentences: one stating the purpose and another detailing parameters. The parameter explanations are front-loaded and efficient, though the formatting with 'Args:' could be slightly cleaner. There's no wasted text, earning its place.

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?

Given the tool has an output schema (which handles return values), the description is moderately complete. However, with no annotations and only basic parameter semantics, it lacks behavioral context like permissions or output structure hints. For a simple list tool, this is adequate but leaves room for improvement in guiding 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?

The description adds meaningful context beyond the schema, which has 0% description coverage. It clarifies that 'course_identifier' can be a Canvas course code (with an example) or ID, and 'assignment_id' is a Canvas assignment ID, providing practical usage hints. However, it doesn't explain where to find these IDs or if they're numeric/string, leaving some gaps.

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 verb ('List') and resource ('submissions for a specific assignment'), making the purpose unambiguous. It distinguishes from siblings like 'list_assignments' by specifying submissions rather than assignments, though it doesn't explicitly contrast with other submission-related tools like 'get_my_submission_status' or 'bulk_grade_submissions'.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer this over 'get_my_submission_status' (for personal submissions) or 'bulk_grade_submissions' (for grading), nor does it specify prerequisites like needing course/assignment access. Usage is implied only by the tool name and parameters.

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