list_announcementsRetrieve all announcements for a Canvas course by providing its course ID, enabling quick access to course updates and communications.
List all announcements in a course.
| Name | Required | Description | Default |
|---|---|---|---|
| course_id | Yes | The Canvas course ID |
Changes observed during successful MCP inspections.
v1.18.11Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v1.18.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already signal read-only and open-world behavior. The description adds the scope ('all announcements in a course') but no additional behavioral context such as pagination, ordering, or whether announcements are a subtype of discussions. No contradiction with annotations.
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?
Single short sentence, front-loaded with the action and object. No wasted 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?
For a one-parameter read-only list tool, the description is mostly sufficient, but it omits any caveats about announcement/discussion overlap, ordering, or pagination that could affect agent expectations.
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 only parameter, course_id, already has a clear schema description ('The Canvas course ID') at 100% coverageebb. The tool description adds no semantic nuance beyond that.
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 uses a specific verb ('List') and resource ('announcements') scoped to a course, so an agent can tell what the tool does. It does not explicitly differentiate this from sibling listing tools such as list_discussions or list_assignments, hence not a 5.
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 description gives no guidance on when to prefer this tool over alternatives, no prerequisites, and no note about how announcements relate to discussions or other list endpoints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.