Canvas LMS 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 of behavioral disclosure. It states the action ('List') and return type ('Dict with favorite course items'), but lacks details on permissions, rate limits, pagination, error handling, or what 'favorite' means in this context. This is a significant gap for a tool with zero annotation coverage.

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 brief return statement. It's appropriately sized with no wasted words, though the return statement could be slightly more informative (e.g., specifying keys in the dict).

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 complexity (a read operation with no parameters), no annotations, and no output schema, the description is incomplete. It doesn't explain the return structure (beyond 'Dict'), authentication needs, or how favorites are defined. For a tool in this context, more behavioral and output details are warranted.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description appropriately doesn't discuss parameters, which is efficient. A baseline of 4 is applied since no parameters exist, and it avoids unnecessary details.

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 ('the current user's favorite courses'), making the purpose specific and understandable. It distinguishes itself from siblings like 'list_courses' or 'list_assignments' by focusing on favorites. However, it doesn't explicitly differentiate from potential similar tools (e.g., 'get_favorites'), though none exist in the sibling list.

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 is provided on when to use this tool versus alternatives. While it's implied for retrieving favorite courses, there's no mention of prerequisites (e.g., user authentication), context (e.g., only available for enrolled users), or comparisons to other tools like 'list_courses' for general course listings.

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