recent_announcements

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds meaningful behavioral detail beyond those flags: the search scope (Announcements/News forum of each current course), ordering (newest first), and the include_all_forums expansion. Lacks any note on pagination or volume limits, keeping it below 5.

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?

Two tightly packed sentences with the core scope front-loaded: time window first, then expansion behavior. Slightly dense but every clause adds information; minimal waste.

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?

Covers the primary use case, default scope, and the key expansion flag across 3 optional parameters, and an output schema exists so return values need not be described. The omission of `course_id` semantics is the main gap for an otherwise complete definition.

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 0%, so the description must carry parameter meaning. It explains `days` as the time window, the implicit course scope, and `include_all_forums` as a scope expander. `course_id` is never mentioned, so one parameter remains unexplained, preventing a 5.

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 resource (announcements from instructors) with explicit scope: last `days` days, current courses' Announcements/News forum. Distinguishes itself from content-oriented siblings like search_course_materials by naming the exact forum and time window.

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?

Describes the default scope and the include_all_forums=true alternative, giving an implicit when-to-use for both modes. Does not name other sibling tools (e.g., search_course_materials) as alternatives for broader searches, so it falls short of explicit when-not guidance.

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