List My Announcements

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds ordering ('newest first'), the cross-course aggregation scope, and the 14-day default window. It stops short of stating pagination/truncation behavior or total-count behavior, which matters for a limit-capped list call.

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?

Three short sentences, scope statement front-loaded, then the sibling routing, then the default window. No filler and no repetition of the schema's parameter documentation.

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 zero-required-parameter read tool with a fully documented schema and readOnly annotation, the description covers scope, ordering, default window, and the sibling alternative. It omits what a returned item looks like (title/date/course/preview), which would be the remaining gap given there is no output schema.

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%, so all five parameters (limit, start_date, end_date, preview_chars, course_identifier) are already documented with formats and defaults. The description's only added parameter-related note, the 14-day default window, restates what start_date's schema entry says. Baseline 3 is appropriate.

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?

States a specific verb and resource ('List announcements') plus an explicit scope ('across ALL your active courses in one call'), which immediately separates it from the per-course sibling. The capitalized ALL signals the aggregation boundary rather than leaving it implied.

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?

Names the alternative and the exact condition that selects it: 'For a single course's full announcement history use list_announcements instead.' It also gives the default time window (last 14 days), so the agent knows what it gets without passing any parameters.

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