canvas_list_announcementsRetrieve Canvas course announcements newest first, defaulting to all active courses over the last 14 days. Filter by course IDs or since date to track recent updates.
Course announcements, newest first. Defaults to all active courses, last 14 days.
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | ISO date, default 14 days ago | |
| course_ids | No | Default: all active courses |
Changes observed during successful MCP inspections.
v2.0.0Does 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 useful behavior (newest-first ordering, default course scope and 14-day window), but says nothing about result volume, pagination, or whether announcements are filtered by enrollment or publication state.
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 compact fragments, zero filler, with the resource and ordering front-loaded before the defaults. Every clause carries information.
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 two-optional-param read-only list tool with full schema documentation and safety annotations, the description covers purpose, ordering, and defaults adequately. The only meaningful gap is result size/pagination behavior, which matters little for a small scoped read.
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 both optional parameters are documented in-schema, so baseline 3 applies. The description's 'last 14 days' and 'all active courses' restate the schema defaults rather than adding new semantics about format or interaction between parameters.
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?
Names the specific resource (course announcements) and its ordering (newest first), which is enough to tell it apart from siblings like canvas_list_assignments or canvas_get_syllabus. It never uses an explicit verb like 'list', relying on the title for that, but the resource scope is unambiguous.
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 default scope ('all active courses, last 14 days') implies when the tool is useful out of the box, but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives such as canvas_whats_new or canvas_changes_since for recent-activity queries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.