Listar eventos de documentos

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered externally. The description adds that results are paginated and carry SIFEN status, which is modest extra context, but says nothing about ordering, volume, or result shape. Reasonable at 3 given the annotation baseline.

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 tight sentences, front-loaded with what is listed and followed by the filter instruction. Nothing 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?

For a read-only paginated list with all three parameters documented and no output schema, the description covers purpose, scope, and filter sourcing adequately. It could add one note on result ordering or pagination semantics to be fully complete.

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 100%, so the baseline is 3, but the description adds genuine meaning for tipoEvento by pointing to listar_enumeraciones as the source of valid values. Pagination parameters are otherwise left entirely to the schema, so it stays just above baseline.

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?

States a specific verb and resource ('Lista los eventos registrados') and enumerates concrete event types (cancelación, inutilización, nominación) plus SIFEN status, so the agent knows exactly what domain is covered. It does not explicitly distinguish itself from the singular sibling 'consultar_evento', which is the only gap keeping it below a 5.

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?

The description tells the agent how to supply the filter ('Filtrá por tipoEvento con un valor de listar_enumeraciones'), which is useful routing. However, it gives no when-to-use guidance relative to alternatives like consultar_evento, so usage is only implied.

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