get_course

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value by enumerating what the response includes (syllabus body, teachers, term, grading periods, progress), which helps the agent anticipate payload weight. It says nothing about enrollment or permission prerequisites, nor whether a missing or inaccessible course errors.

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 short sentences with the purpose front-loaded and the returned contents following immediately. Nothing is redundant or padded.

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?

An output schema exists, so return values need not be fully explained, and the description's field list is a useful complement. However, with an undocumented required parameter and a crowd of similar course-level siblings, the definition leaves out the ID source and the routing rationale an agent needs to call it confidently.

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 0% for the single required parameter course_id, so the description must carry the burden. It only says 'by ID' and never states what kind of ID this is or where to obtain it, for example from list_all_courses. This is a meaningful gap for the one parameter the agent must supply.

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 and resource: 'Get detailed info for a single course by ID.' The singular 'single course by ID' implicitly distinguishes it from the many list_* siblings such as list_all_courses and list_active_courses, but no sibling is named explicitly.

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?

There is no guidance on when to choose this tool over near neighbors like canvas_course_home, canvas_browse_course, or catch_me_up_on_course, all of which also surface course-level detail. The use case is only implied by the phrase 'single course by ID'.

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