Canvas MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions filtering and sorting capabilities but fails to describe critical behaviors: whether it's read-only (implied by 'List'), pagination or rate limits, authentication requirements, error handling, or the structure of returned data. For a tool with 5 parameters and no annotations, this leaves significant gaps in understanding how it operates.

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 well-structured and appropriately sized: a clear purpose statement followed by a parameter list with brief explanations. Each parameter description is concise and adds value. However, the formatting with indentation and bullet-like 'Args:' might be slightly verbose, and it could be more front-loaded with key usage notes, but overall it's efficient.

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 (5 parameters, no annotations, but with an output schema), the description is partially complete. It excels in parameter semantics but lacks behavioral context (e.g., safety, performance) and usage guidelines. The presence of an output schema means return values are documented elsewhere, reducing the burden, but the description should still cover operational aspects like authentication or limitations to be fully adequate.

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%, so the description must compensate fully. It successfully adds meaning beyond the schema by explaining all 5 parameters: 'course_identifier' is clarified with an example (Canvas course code or ID), 'sort' and 'order' define criteria and direction, 'search_term' specifies where to search (title or body), and 'published' explains the filter options (True, False, None). This provides complete semantic context that the schema lacks.

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: 'List pages for a specific course.' It specifies the verb ('List') and resource ('pages'), and distinguishes it from siblings like 'get_page_content' or 'get_page_details' by focusing on listing rather than retrieving details. However, it doesn't explicitly differentiate from similar listing tools (e.g., 'list_assignments'), which prevents a perfect score.

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 prerequisites (e.g., needing course access), compare it to siblings like 'list_module_items' or 'get_front_page', or specify scenarios where it's preferred. The absence of usage context leaves the agent without direction on tool selection.

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