ultimos_eventos

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

No annotations are provided, so the description must carry the full burden. It discloses the core behavior (returning events with seq > desde_seq) and its polling nature. However, it does not explicitly state whether the operation is read-only, idempotent, or if there are any side effects. For a simple retrieval tool, this is acceptable but leaves gaps.

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 consists of two concise sentences. Every word serves a purpose, defining the input filter and the intended use case. There is no redundancy or unnecessary detail.

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?

The tool has an output schema, so the description does not need to detail return values. The description is adequate for a simple polling tool, covering the purpose and key parameter. It could be more complete by mentioning that it returns only new events, but given the output schema existence, it is sufficiently complete for an AI agent.

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 description explains the meaning of desde_seq ('seq mayor a desde_seq'), adding value beyond the schema's parameter name and default of 0. However, it does not describe sesion_id, which is required. With 0% schema description coverage, the description should cover more parameters; it only partially compensates.

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 clearly states the tool returns events with seq greater than desde_seq, positioning it as a polling primitive for live discussions. The verb 'eventos' (events) and the specific filtering condition differentiate it from sibling tools like crear_sesion (create session) and consultar (general query). However, it doesn't explicitly name the resource (e.g., 'session events'), which slightly reduces specificity.

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 labels the tool as a 'polling primitive for live discussion,' implying it should be used when an agent needs to query for new events since a known sequence number. It does not mention when to avoid using it (e.g., if full event history is needed) or suggest sibling tools like consultar as alternatives. The guidance is present but implicit.

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