List course files

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

Annotations already declare read-only, idempotent, and non-destructive. The description adds that locked/hidden folders are excluded automatically, which is a valuable behavioral detail beyond the safety profile. This informs the agent that results may be incomplete for inaccessible files.

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 with zero waste. The purpose is front-loaded, and the behavioral note is concise. Ideal length for a simple list operation.

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 low-complexity list tool with full annotation coverage and no output schema, the description conveys purpose and a key behavioral caveat. It could optionally mention recursion or pagination, but those are not critical for basic usage. Essentially 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?

Schema description coverage is 100%, with both parameters (courseId and searchTerm) having clear descriptions. The description adds no parameter-specific meaning beyond the schema, so it does not compensate for or expand on the existing parameter documentation. Baseline 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?

States the verb 'list' and resource 'files in a course' precisely. It clearly distinguishes from sibling canvas_list_course_folders (folders) and canvas_get_file (single file) by naming the specific resource. The additional note about locked/hidden folders adds useful specificity.

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 purpose implies when to use (when course files are needed), but there is no explicit differentiation from similar tools like canvas_list_course_folders. The note about exclusion hints at a limitation but does not guide the agent to alternatives or when not to use this tool.

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