download_course_file

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

Annotations indicate readOnlyHint=true, and the description aligns by describing a download action. It goes beyond annotations by specifying the default behavior for save_directory (system temp dir) and the precondition that the directory must exist.

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 concise, front-loaded, and uses a structured format (Args section). Every sentence earns its place with no redundancy.

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 straightforward nature of the tool and presence of an output schema, the description is mostly complete. It could mention potential errors (e.g., file not found) but is adequate for an AI agent.

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?

Though schema description coverage is 0%, the description provides meaning for save_directory (default, existence requirement) and implicitly explains course_identifier and file_id. This adds value beyond the bare schema.

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 action ('download') and the resource ('file from a Canvas course to the local filesystem'). It is a specific verb+resource combination that distinguishes it from siblings like 'read_course_file' and 'upload_course_file'.

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?

It advises using list_course_files or list_module_items to find file IDs, providing context for obtaining the required file_id parameter. However, it does not explicitly state when to use this tool versus alternatives like read_course_file.

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