list_course_files

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

readOnlyHint correctly signals a safe read, and the description does not contradict it, but it adds little behavioral detail beyond 'optional search'. There is no disclosure of pagination, result scope, or file metadata vs content.

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 states the resource and key capability without repetition or filler.

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-only listing tool with fully documented schema and a readOnly annotation, the description is adequate. However, without an output schema, it could usefully mention what the returned file list contains or any size limits.

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%, so the schema already documents all four parameters. The description's 'optional search' only echoes search_term and contributes no additional semantic detail.

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?

Description clearly identifies the action ('List'), the resource ('files in a Canvas course'), and an optional behavior (search). This distinguishes it from file-content siblings like download_course_file, 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?

The operation is implied by the verb 'List' but there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives for retrieving or uploading files. The 'optional search' hints at the search_term parameter but does not define use cases or exclusions.

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