blackboard_get_announcement

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only a hint that the announcement must be accessible and that text and dates are returned; it says nothing about permission failures or what happens when the announcement is not accessible.

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?

A single short sentence with no padding, which is good, but it is under-specified rather than genuinely concise — it omits the details that would make the sentence earn its place.

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, two undocumented required parameters, and no guidance on the ID formats or access constraints, the description leaves significant gaps for an agent to fill by trial and error. A read-by-ID tool needs at least the identifier contract spelled out.

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 description carries the full burden for two required parameters. 'De la sección indicada' loosely maps to courseId and 'un anuncio' to announcementId, but neither the ID format (the ^_\d+_\d+$ pattern) nor any required relationship between them is explained.

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 identifies the resource (an announcement) and the returned content (text and dates), so the purpose is inferable, but the verb is implicit and it never distinguishes this single-item fetch from siblings like blackboard_list_announcements or blackboard_search_announcements. It is adequate but not specific enough for an agent to route confidently.

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 statement of when to use this tool versus the list or search announcement variants, and no prerequisites beyond the vague qualifier 'accesible'. The agent must infer that this is the by-ID detail fetch while the siblings handle listing and searching.

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