Canvas MCP Server

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

With no annotations provided, the description carries the full burden. It discloses the return format (detailed information with specific fields like type, title, completion requirements), which is valuable behavioral context. However, it doesn't mention potential limitations like pagination, rate limits, or authentication needs, leaving gaps for a read operation.

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 front-loaded with the core purpose in the first sentence, followed by a bulleted list of return details that efficiently elaborates without redundancy. Every sentence earns its place, and the structure is clear and well-organized.

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's moderate complexity (2 required parameters, no output schema, no annotations), the description is mostly complete. It clearly states the purpose and return format, but lacks information on error handling, pagination, or authentication, which could be useful for a list operation in an educational context.

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 100%, so the schema already documents both parameters ('course_id' and 'module_id'). The description adds no additional parameter semantics beyond implying these IDs are needed to specify the module. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 specific action ('List all items') and resource ('within a specific module'), and distinguishes it from siblings like 'canvas_module_get' (single module) and 'canvas_module_list' (all modules). It provides precise scope by specifying 'all items' within a module.

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 when needing items in a module, but lacks explicit guidance on when to use this versus alternatives like 'canvas_assignment_list' or 'canvas_quiz_list' for specific item types. No exclusions or prerequisites are mentioned, though the required parameters suggest it's for module-level queries.

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