List announcements

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

With no annotations provided, the description carries the full behavioral burden, and it delivers: it discloses that only headers are returned, that results are newest-first, that course_id scopes vs. aggregates, the exact tile shape, the Taipei timezone format, and that credentials come from MCP settings rather than the agent. This gives the agent a clear model of what the tool does and what it returns.

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 compact and well-organized: it leads with the core purpose and distinction from get_announcement, then covers parameter behavior, return shape, timezone, and authentication. Every sentence adds value with no redundancy or filler.

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?

Despite having no output schema and no annotations, the description is self-sufficient: it explains what is returned, how pagination works, how course_id scopes the result, what each tile contains, and where credentials come from. An agent can invoke this tool correctly without needing additional context.

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?

Although the schema already covers 100% of parameters, the description adds meaningful semantics beyond the schema: course_id is said to come from list_courses and omitting it aggregates across current-semester courses, and limit/offset are tied to the newest-first pagination behavior. This enriches the agent's understanding of how to invoke the tool correctly.

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 the tool lists announcement tiles (headers only, no message body) from a course's Announcements forum, using the specific verb 'List' and a well-defined resource. It also distinguishes itself from get_announcement by explicitly directing the agent to call that sibling to read a full announcement, making the purpose unambiguous.

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 explicit guidance on when to use this tool: it is for scanning announcement tiles, and reading a full announcement requires get_announcement using the discussion_id. It also explains the course_id behavior (specific course vs. aggregate across current-semester courses), which tells the agent exactly how to choose parameters.

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