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 describes the transformation behavior (parsing JSON to extract violations) and mentions the return format, but lacks details on error handling, performance characteristics, or data validation requirements. It adequately covers the core operation but misses some behavioral nuances.

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?

Perfectly structured with a clear purpose statement, usage context, parameter explanation, and return value description in four concise sentences. Every sentence adds value with zero redundancy, and information is logically front-loaded.

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 has an output schema (which handles return value documentation), the description provides excellent context about purpose, usage, and parameters. It's complete enough for understanding when and how to use this parsing tool, though additional behavioral details could enhance it further.

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. It clearly explains the single parameter 'report_json' as 'JSON string from fetch_ufixit_report containing the report,' providing essential context about the expected format and source. However, it doesn't detail the JSON structure or validation requirements.

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 ('parse'), resource ('UFIXIT report content'), and outcome ('extract accessibility violations'). It distinguishes from its sibling 'fetch_ufixit_report' by specifying it processes that tool's output, establishing a clear workflow relationship.

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?

Explicitly states when to use this tool: 'Takes the output from fetch_ufixit_report' and provides the purpose 'for analysis and remediation.' This gives clear prerequisites and context, distinguishing it from other accessibility-related tools like 'scan_course_content_accessibility' or 'format_accessibility_summary'.

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