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 mentions 'List all peer review assignments' but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, error conditions, or what 'all' means in practice. The description is minimal and lacks operational context.

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 sized with a clear purpose statement followed by parameter details. The two-sentence structure is efficient, though the parameter explanations could be slightly more integrated into the main description.

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 that there's an output schema (which handles return values), the description is moderately complete for a read-only list operation. However, with no annotations and minimal behavioral disclosure, it leaves gaps in understanding how the tool behaves in practice beyond basic parameter semantics.

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%, but the description adds meaningful semantics: it explains that 'course_identifier' can be a code or ID with an example, and 'assignment_id' is a Canvas assignment ID. This compensates somewhat for the lack of schema descriptions, though it doesn't cover all potential nuances.

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 the resource 'peer review assignments', specifying it's for a 'specific assignment'. It distinguishes from siblings like 'get_peer_review_assignments' by focusing on assignments rather than general peer reviews, but doesn't explicitly contrast with all similar tools.

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?

No guidance on when to use this tool versus alternatives like 'get_peer_review_assignments' or 'list_assignments'. The description only states what it does, not when it's appropriate or what prerequisites might exist.

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