canvas_download_file

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

The destructiveHint annotation already warns of side effects, and the description adds that the URL comes from canvas_list_course_files. However, it does not disclose the overwrite parameter's behavior, whether directories are created, or other filesystem effects. This is partial but not rich behavioral context.

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-loaded with the purpose, and contains no fluff. Each sentence adds essential information: the action and the required input constraints.

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?

While the tool is relatively simple and the source of URL is specified, the description does not address the overwrite parameter's effect, the return value (no output schema), or error conditions. The destructive annotation covers safety, but the agent still lacks details about file overwrite behavior, making the description only partially complete.

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 description adds meaning by explaining that 'url' is the absolute URL from canvas_list_course_files, which is helpful. However, it does not explain the 'overwrite' parameter, which has no schema description. With 67% schema coverage, the description partially compensates but leaves a key parameter ambiguous.

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 action ('Download a Canvas file to disk') with a specific verb and resource. It distinguishes this tool from siblings by referencing the source of the URL (canvas_list_course_files), making its purpose unambiguous.

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 a clear prerequisite: the 'url' must come from canvas_list_course_files, and 'destinationPath' is required. This guides the agent on how to prepare inputs, though it does not explicitly mention when not to use it or list alternatives. The context is sufficient for correct usage.

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