List course announcements

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety. The description adds the behavioral qualifier 'recent', implying the tool returns only recent announcements, not all. This goes slightly beyond annotations but does not specify what 'recent' means or the exact return structure, so the incremental value is moderate.

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 a single short sentence, 'Recent announcements for a course.' It is front-loaded with the core purpose and contains no redundant words or filler. It is appropriately sized for a tool with only one parameter and a clear action.

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?

Given the tool's simplicity (one parameter, no output schema), the description is mostly adequate but leaves ambiguity around the term 'recent'—there is no explanation of the time window or any limits. Since there is no output schema, a bit more detail about what announcements are returned (e.g., title, date) would improve completeness, but the name and description cover the basic intent.

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% because the only parameter, courseId, has a description ('Canvas course id') in the schema. The tool description itself does not mention parameters or add any extra meaning beyond what the schema already provides, so the baseline of 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?

The description clearly states the tool lists recent announcements for a course, identifying both the resource (course announcements) and the action (list/recent). The title 'List course announcements' reinforces this, and no sibling tool targets announcements, so it is distinct.

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 provides no explicit guidance on when to use this tool versus alternatives, nor any context or exclusions. While it is the only announcement tool among siblings, the description itself does not say 'use this when you need course announcements' or mention any prerequisites, leaving usage entirely to inference.

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