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 the tool returns items 'needing action' and is for 'quick view,' but lacks details on permissions (e.g., instructor vs. student access), rate limits, pagination, or error handling. For a read operation with zero annotation coverage, this leaves significant behavioral gaps, though it doesn't contradict anything.

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 three sentences: purpose statement, return examples, and usage context. It's front-loaded with the main function and avoids redundancy. However, the second sentence could be integrated more smoothly, and there's minor wordiness ('that need attention' could be trimmed).

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 no annotations, no output schema, and a simple input schema, the description provides basic purpose and usage but lacks details on return format (e.g., structure of items), error cases, or authentication needs. It's adequate for a minimal tool but incomplete for robust agent use, as behavioral transparency is weak.

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%, with one optional parameter 'course_id' documented in the schema as limiting to a specific course. The description doesn't add any parameter details beyond this, so it relies on the schema. With high coverage, the baseline is 3, as the description doesn't compensate but doesn't need to heavily.

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 tool's purpose: 'Get your TODO list items that need attention' with specific examples (assignments to submit, items to grade, unread discussions). It distinguishes from siblings like canvas_assignment_list or canvas_missing_submissions by focusing on a curated 'immediate attention' view, though not explicitly named. The verb 'Get' is clear but could be more precise like 'Retrieve'.

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 context: 'for a quick view of what needs immediate attention,' suggesting it's for prioritization over comprehensive lists. However, it doesn't explicitly state when to use this vs. alternatives like canvas_planner_items or canvas_missing_submissions, nor does it mention exclusions or prerequisites. The guidance is helpful but not fully comparative.

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