get_announcementsRetrieves all school announcements with full text for a specified Librus account without marking them as read.
Get all school announcements with their full text. Does not mark them read in Librus.
| Name | Required | Description | Default |
|---|---|---|---|
| account_alias | Yes | Login alias from list_accounts. |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | ||
| identity | Yes | ||
| pagination | No | ||
| observation | Yes |
Changes observed during successful MCP inspections.
v2.5.0Output schema / $defs / Pagination / additionalPropertiesRemoved value: -falseOutput schema / additionalPropertiesRemoved value: -falsev2.3.1Input schema / properties / account_alias / descriptionAdded value: +"Login alias from list_accounts."Input schema / properties / account_alias / patternPrevious value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuinely non-obvious side-effect disclosure: announcements are not marked read in Librus, which matters for agents worried about mutating read state. It does not discuss volume or pagination, but an output schema exists.
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 short sentences, purpose front-loaded, second sentence carrying the only non-redundant caveat. Nothing wasted and nothing buried.
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 single-parameter read tool with an output schema and full schema coverage, the description covers what is returned (full text) and the key side-effect behavior. Only minor gaps remain, such as whether results are limited or paginated.
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?
There is one parameter, account_alias, and schema coverage is 100% with the schema already pointing to list_accounts for the value. The description adds no meaning beyond the schema, so the baseline of 3 applies.
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 ('Get all school announcements') plus the scope detail that full text is returned. It is clearly distinguishable from siblings like get_messages or get_notification_status, though it does not name an alternative explicitly.
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?
Usage is implied — fetch announcements versus other content types — but there is no explicit when-to-use/when-not guidance and no sibling is named as an alternative. The 'does not mark them read' clause hints at a comparison but never states it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.