get_course_files

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

Since annotations are absent, the description carries the full burden. It accurately describes the operation but does not disclose read-only nature, error behavior, or edge cases. It adds only basic functional context.

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 concise and front-loaded, with the main purpose in the first sentence and parameters clearly listed. No unnecessary words.

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 an output schema exists, return structure is defined externally. The description covers the core functionality and key parameters, but misses the account parameter and explicit usage guidance, making it slightly incomplete for full agent decision-making.

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?

The description explains course_id and folder_path with usage details and examples, adding meaning beyond the schema which has 0% coverage. However, it omits the account parameter entirely, leaving one of three parameters unexplained.

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 'List files in a Canvas course' with clear verb and resource, and mentions optional folder scoping. It does not explicitly differentiate from sibling tools like read_course_file, but the verb 'list' distinguishes it inherently.

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?

It provides a helpful hint that course_id should come from get_courses, but does not give explicit when-to-use vs when-not-to-use guidance relative to siblings like read_course_file. Usage is implied rather than explicitly contrasted.

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