Get File

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

Annotations already declare readOnlyHint and openWorldHint, covering the read-only nature. The description adds the concrete behavioral detail that the response includes a download URL, which is not evident from annotations or schema. This is useful beyond the structured data.

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?

A single, front-loaded sentence with zero filler. It efficiently conveys the core purpose and a key response feature without 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?

For a simple read operation with two well-documented parameters and no output schema, the description is largely sufficient. It mentions the download URL, hinting at the response shape, but does not address error conditions or explicit differentiators from related tools. However, given the low complexity and strong annotations, this is a minor gap.

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 coverage is 100% with both parameters having clear descriptions ('The Canvas file ID' and 'The Canvas course ID'). The tool description adds no additional parameter context, so it neither improves nor detracts from what the schema provides. Baseline of 3 is appropriate.

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 states a specific verb ('Get'), resource ('metadata for a single file'), and identifier ('by ID'), and adds the key detail that the response includes a download URL. This clearly differentiates it from siblings like list_files (multiple files) and download_file (file content).

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 implies usage for a single file when the ID is known, but it does not explicitly state when not to use it or mention alternatives. It does not say 'for multiple files, use list_files' or 'for file content, use download_file', leaving the agent to infer the appropriate context.

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