Get file download link

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the behavior as a safe read operation is clear. The description adds that the URL is temporary and expires, which is useful beyond what annotations provide. It doesn't describe rate limits or auth requirements, but these are minor for a simple read tool.

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?

Two sentences, zero wasted words. The first sentence states the action and source of the ID, the second provides a critical usage note about expiration. Every sentence earns its place.

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 only 1 parameter, good annotations, and no output schema, the description covers the essential behavioral aspects. The temporary nature of the URL is important and disclosed. It could mention the return format (URL string) slightly more explicitly, but it's clear enough.

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 100%. The description mentions the source of the file_id (canvas_list_files or module items), which adds slight context beyond the schema's 'Canvas file ID'. However, the schema itself already handles the parameter definition adequately.

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 uses the specific verb 'Get' and the resource 'temporary authenticated download URL for a file'. It clearly distinguishes this tool from siblings like canvas_list_files (which lists files) and canvas_read_file (which likely reads file content directly). The description immediately identifies the purpose and the expected input.

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 explicitly states that the 'file_id' comes from 'canvas_list_files or module items', giving clear usage context. It also notes the URL expires and to use it promptly, which implies when to download the file. However, it does not explain when NOT to use this tool versus alternatives like canvas_read_file or canvas_export_course.

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