blackboard_list_announcements

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no mention of pagination, result scope, ordering, or the course-scoped nature of the listing.

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?

Three words is terse, but this is under-specification rather than genuine conciseness. There is no front-loaded statement of what the tool does or returns, so the brevity conveys no value.

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?

With no output schema, no parameter documentation, and only annotation hints for behavior, the description must carry the burden — and it does not. An agent cannot tell what this returns, how it differs from get_announcement or search_announcements, or what courseId should look like.

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?

The single required parameter courseId has 0% schema description coverage, so the schema provides no explanation of its meaning or the '^_\d+_\d+$' pattern. The description does not compensate at all — it never mentions courseId, its required status, or its format.

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 'Anuncios del curso' is a noun phrase that essentially restates the resource already implied by the name 'blackboard_list_announcements'. It adds a scope qualifier ('del curso') but no verb, and does nothing to distinguish it from siblings like blackboard_search_announcements, blackboard_get_announcement, or blackboard_list_institution_announcements.

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 whatsoever about when to use this tool versus the many sibling announcement tools (search_announcements, get_announcement, list_institution_announcements, search_multi_course_announcements). No prerequisites, no context, no exclusions.

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