obs_get_announcementsFetch announcements published in OBS. Filter results by page and limit to retrieve specific sets, resolving the need to access current course updates.
Return announcements published in OBS.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| limit | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does 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 only states it returns announcements, implying a read operation, but does not disclose pagination behavior, authentication requirements, or any other traits. It is minimal and does not go beyond what the name implies.
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 wasted words, which is appropriately front-loaded. It is efficiently structured, though it might be under-specified for the overall task, but the structure itself is clean.
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?
Given the presence of an output schema and only two optional parameters, the tool is relatively simple, but the description is too sparse to fully contextualize its use. It does not explain when to prefer it over similar sibling tools, nor does it mention any prerequisites or expectations. The minimalism leaves the agent guessing about the scope and usage.
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 schema provides no parameter meanings, and the description does not mention the page or limit parameters at all. With two parameters and no descriptions, the tool fails to compensate for the lack of semantic guidance, making it difficult for an agent to understand how to use them.
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 action ('Return') and resource ('announcements published in OBS'), making the purpose understandable. It distinguishes from siblings like get_course_announcements or get_dashboard_announcements by specifying 'OBS' as the source, though it does not explicitly contrast with them. This is clear but not fully differentiated.
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?
There is no guidance on when to use this tool versus alternatives such as get_course_announcements or get_dashboard_announcements. The description is a bare statement with no contextual cues about preferred scenarios or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.