Export course to markdown

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: that the export is a single markdown document containing specific elements. It does not contradict annotations and adds context about output format and scope beyond the structured fields.

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 two sentences long, front-loading the purpose and content list, followed by a use-case sentence. No unnecessary words or repetition.

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 simple single-parameter tool and no output schema, the description adequately explains what the return value contains (markdown document with listed sections) and its intended use (archiving). It does not cover error cases or size limits, but these are minor given the overall clarity.

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?

With 100% schema description coverage (the only parameter 'course_id' is described as 'Canvas course ID'), the description does not add further parameter semantics. Baseline of 3 is appropriate since schema already handles documentation.

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 'export' and resource 'course', specifies the output format ('single markdown document'), and lists the included components (details, syllabus, grade, assignments, modules, announcements). This distinguishes it from sibling tools that focus on single components.

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 clear context: it's a 'one-shot export' designed for archiving to Notion or notes apps. It implies use when a comprehensive snapshot is needed, but does not explicitly state when not to use it or name alternative tools for partial exports.

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