get_announcements

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds scope (all active enrolled courses) and recency (recent announcements) but does not explicitly state read-only behavior, pagination, or what 'recent' means. It does not contradict any annotations because none exist.

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, concise sentence with no filler. It front-loads the purpose and scope, making it easy to parse. Every word earns its place.

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 list tool, the description is minimal but incomplete. It omits explanation of the 'account' parameter, any ordering or pagination details, and the exact meaning of 'recent' or 'active enrolled courses'. While an output schema exists (so return format is covered), the description still leaves functional ambiguity, especially regarding parameter semantics.

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 compensate for the undocumented parameter. The only parameter 'account' is not explained at all; the description does not clarify how it affects the query or what values it accepts. This leaves the agent guessing about its role, which is a significant gap.

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 a specific verb (list) and resource (announcements) with a defined scope (all active enrolled courses). It is distinct from siblings like get_course_discussions or get_course_pages, making it unambiguous which resource the agent is retrieving.

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 conveys its purpose clearly but does not explicitly mention alternatives or when not to use it. However, given the sibling tool names, the agent can infer that this tool is for announcements specifically, and no other tool targets this resource. It provides clear context without exclusions.

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