Read Course File

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

Adds substantial context beyond annotations: format support, 25 MB limit, pagination via next_offset, and the key failure mode that scanned PDFs have no text. Annotations already cover read-only/idempotent, and the description does not contradict them.

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?

Five short sentences, each carrying unique information: purpose, safety, format/limits, pagination behavior, and preconditions. Front-loaded with the core verb.

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?

No output schema, but the description covers everything an agent needs: what's returned (text), limits, pagination continuation, known failure case, and parameter sourcing. Nothing material is missing for a read tool with full annotations.

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% and the schema already documents offset, max_chars, and file_id. The description reinforces pagination ('call again with next_offset') but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

Specific verb+resource ('Read the text of a Canvas file') with the supported formats and purpose enumerated. It is clearly distinguished from download_file, get_file_metadata, and list_course_files by extracting text content for summarization/quizzing.

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?

States the use case (summarize, quiz, answer questions) and tells the agent where to get file_id ('list_course_files or list_module_items'), but does not explicitly steer away from download_file or get_page_content for text-like content.

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