uned_novedades

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the content categories returned (entregas, eventos, anuncios), but says nothing about the look-ahead window that governs the output, the read-only nature of the operation, or any auth requirement — the temporal behavior is the most important undisclosed trait.

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 with the content scope front-loaded and the use-case trigger second; no filler. It is terse enough that it sacrifices needed detail, but nothing in it is wasted.

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?

An output schema exists, so return values needn't be explained. However, for an aggregator that overlaps three sibling tools, the absence of any routing guidance and the undocumented "dias" parameter leave meaningful gaps for correct invocation.

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, so the description is the only place its meaning could be explained. "Próximas entregas" hints at a forward-looking window but never states that "dias" controls the number of days ahead, nor mentions the default of 7.

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 states a specific resource agregado: "próximas entregas + eventos + anuncios nuevos", which tells an agent exactly what content the tool returns. It implies aggregation via "Resumen", distinguishing it implicitly from the single-purpose siblings (uned_entregas, uned_eventos, uned_anuncios), though it never names them or confirms it supersedes them.

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?

"Ideal para '¿qué tengo pendiente?'" gives a concrete trigger scenario, which is better than nothing. But it offers no exclusion or alternative guidance — an agent can't tell from the description whether to call this or the three sibling tools individually, nor whether it requires an authenticated session first.

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