uned_anuncios

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

No annotations are provided, so the description carries the full disclosure burden. It implies a read-only retrieval, but says nothing about authentication requirements, ordering, pagination, or how many announcements are returned, which matters for a listing tool.

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 sentence with no filler that front-loads the resource and its scope. It is efficient, though it is terse to the point of omitting guidance rather than being optimally structured for a tool with a filter parameter.

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?

Because an output schema exists, return-value explanation is not required, and for a simple listing tool the description is minimally sufficient. However, the undocumented 'dias' parameter and the absence of any routing guidance against sibling tools leave real gaps.

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 parameter 'dias' has 0% schema description coverage and a default of 7, so its meaning must come from the description — but the text only says 'Últimos' without explaining that the window is expressed in days. The link between the parameter and the recency scope is left to inference.

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 names a specific resource (announcements from teachers in each course's notice forum) and a scope (most recent), so an agent understands what it retrieves. It does not explicitly contrast itself with the nearby siblings uned_foros or uned_novedades, which is the main gap.

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 call this versus alternatives, even though uned_foros and uned_novedades appear to cover adjacent ground. The only implied guidance is the word 'Últimos', which hints at recency but sets no condition.

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