canvas_list_announcements

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

Annotations already declare readOnlyHint and non-destructive behavior; the description explicitly reinforces this with 'All requests use Canvas GET endpoints; this server cannot modify Canvas,' adding natural-language clarity beyond the hints, though no additional behavioral details like rate limits are given.

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 short but contains redundancy: the first two sentences both express read-only behavior. The third sentence delivers the core purpose. Could be more concise by merging the first two.

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 simple list tool with no output schema, the description covers scope (one/all courses) but omits details like return fields, pagination, or how 'recent' is determined. It is adequate but not fully complete.

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 schema provides no descriptions (0% coverage). The description hints at course_id via 'one or all active courses' and recency for since_days, but it does not explicitly explain either parameter's semantics, ranges, or defaults. It adds some meaning but leaves gaps.

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 clearly states the tool lists recent announcements for one or all active courses, using the specific verb 'list' and resource 'announcements'. This distinguishes it from sibling tools like canvas_list_courses and canvas_list_assignments.

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 implies use when announcements are needed and clarifies that it works for a single course or all active courses, but does not explicitly name alternative tools for other resources or state when not to use.

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