get_announcements

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

With readOnlyHint and openWorldHint already provided by annotations, the description adds meaningful behavioral details: results are ordered newest first, returned as Markdown, and scoped to current courses when no course filter is supplied. This goes beyond the annotations and helps the agent predict the output shape.

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 one short, front-loaded sentence with no filler. It packs the core facts—resource, ordering, output format, and scoping rule—into minimal text, earning every word.

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 read-only list tool with no output schema, the description covers format, ordering, and scope succinctly. It does not describe the shape of each announcement item, but the schema annotations and low complexity make this acceptable. It is nearly complete for safe invocation.

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 75%, and the schema already documents days, full, and course with useful descriptions. The description adds only the 'current courses' interpretation of omitting course, which reinforces the schema but does not meaningfully expand parameter knowledge. The undocumented limit parameter is not compensated for.

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 identifies the resource (course announcements) and specifies key behavior: newest first and Markdown format. It is immediately distinguishable from sibling tools like get_assignments, get_content, and get_discussions by naming a distinct resource and its presentation.

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 one useful usage clue: 'Omit course for all current courses.' However, it does not explicitly say when to prefer this tool over sibling announcement-like tools, nor does it mention any exclusions or alternatives. The usage context is implied rather than fully stated.

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