canvas_read_file

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds 'All requests use Canvas GET endpoints; this server cannot modify Canvas,' which reinforces the annotation but adds little extra behavioral context such as authentication, error behavior, or download size limits.

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 key read-only context, and contains no filler. Every word contributes to explaining the tool's scope and safety.

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?

For a simple two-parameter read-only tool with ample annotations, the description covers safety and basic scope. However, it leaves ambiguity about the return format (file content vs. metadata/URL) and the exact download behavior, making it incomplete for an agent deciding how to invoke and interpret the result.

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%, and the description only implies that course_id identifies the course and file_id identifies the file. It does not explain how to obtain these IDs or clarify the relationship beyond 'belongs to a course,' so it fails to compensate for the lack of schema descriptions.

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 a specific verb 'Read or safely download' with a clear resource ('one file that belongs to a course'), distinguishing it from sibling list tools like canvas_list_files. This makes the tool's purpose immediately understandable.

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 read-only context and 'one file' phrasing imply when to use the tool, but there is no explicit when-not guidance or reference to alternatives such as canvas_list_files for discovering file IDs. The usage guidance is present only implicitly.

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