s21_get_announcements

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

With no annotations, the description carries the disclosure burden. It does reveal one meaningful behavioral trait: output is returned as clean Markdown text. However, it does not state that the operation is read-only, how the optional filter behaves, or any authentication or error behavior, leaving important gaps.

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?

One focused sentence with no filler. The core action, resource, and key output characteristic are front-loaded, and every word contributes meaning.

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 tool with one optional parameter and no output schema, the description covers purpose and output format. Yet it omits the default behavior when no course_ids are supplied, and it does not help an agent choose this tool confidently among many academic-content siblings.

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% — the single optional `course_ids` parameter is already documented in the schema. The description adds no extra parameter meaning beyond that, so the baseline of 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?

The description states a specific verb ('Obtiene'), a clear resource ('avisos y anuncios publicados por profesores'), and a distinctive output trait ('con texto limpio en Markdown'). It clearly differentiates from sibling tools like s21_get_discussion_topics or s21_get_assignments by subject matter.

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 no guidance on when to use this tool versus siblings such as s21_get_discussion_topics or s21_get_upcoming_events. There are no exclusions, prerequisites, or alternative routing hints; usage must be inferred entirely from the noun 'anuncios'.

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