Consultar un evento

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

With no output schema, the description usefully discloses what the call returns (status APROBADO/RECHAZADO, response code and message). Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuine return-value context beyond them.

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 with the identification-and-return detail front-loaded and the usage hint second. No redundant or filler text.

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 single-id read-only lookup with no output schema, the description covers both what it returns and when to use it, which is nearly everything the agent needs. Minor gap: it doesn't state behavior when the id does not exist.

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 single eventoId parameter is fully documented in the schema and the description only restates its meaning (eventoSifenId). Baseline 3 is appropriate when the schema does the heavy lifting.

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 (detalle de un evento por su id) and enumerates exactly what it returns (estado, código, mensaje de respuesta de SIFEN). This clearly differentiates it from the sibling listar_eventos, which lists rather than fetches a single event by id.

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 final sentence gives an explicit use case: confirm the result of a cancelación, nominación, or inutilización. It tells the agent when to reach for this tool, though it doesn't name an alternative tool for other scenarios (e.g. listing events).

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