List Announcements

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only 'all' and 'in a course', which is minimal extra behavioral context beyond what annotations and the course_id parameter already imply. No additional traits like return format, pagination, or filtering behavior are disclosed, but none contradict the 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?

The description is a single, front-loaded sentence with no filler. Every word contributes meaning: 'List', 'all', 'announcements', 'in a course'.

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, one-parameter, read-only list tool with readOnlyHint and openWorldHint annotations and no output schema, the description is complete. It clearly conveys the operation and scope, and nothing critical is missing for selecting and invoking the tool.

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 100% (course_id is fully described as 'The Canvas course ID'). The description repeats the course concept but does not add new meaning beyond the schema. The baseline of 3 applies when the schema handles parameter documentation.

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') with a clear resource ('all announcements') and scope ('in a course'). It unambiguously states what the tool does and is distinct from sibling tools like list_discussions or list_calendar_events.

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 implies usage: call this when you need announcements for a given course. However, it provides no explicit guidance on when to prefer this over alternatives, prerequisites, or pagination/result-limit considerations. There is no sibling announcement tool, so the lack of explicit alternatives is less critical, but still missing.

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