Eva Avisos

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

With no annotations, the description carries the behavioral burden and does disclose the source ('foro') and that only the latest notices are returned. It does not mention authentication, ordering, or side effects, but for a simple read/list operation with an output schema present, this is adequate though not rich.

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 short sentence with no filler. The most important scoping information is front-loaded, making it easy to parse quickly.

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 sibling list and absence of annotations, the description does not clarify how eva_avisos differs from eva_aviso, offers no usage guidance, and leaves 'limite' undefined. The output schema covers return shape, but the missing contextual and parameter information makes the definition incomplete.

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 parenthetical 'nombre, código o id' adds useful meaning to the 'curso' parameter beyond the bare string schema. However, 'limite' is not described at all, so with 0% schema description coverage the description only partially compensates for the missing parameter documentation.

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 ('avisos del foro') and the scope ('un curso'), and clarifies that the course can be specified by name, code, or id. It lacks an explicit verb like 'obtiene' or 'lista', but the plural 'avisos' makes the retrieval intent clear and distinguishes it at least implicitly from the singular sibling eva_aviso.

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?

No guidance is given about when to use this tool instead of eva_aviso or the other course-related tools. There are no conditions, exclusions, or alternatives mentioned.

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