Leer mensajes de una sesión

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

No annotations are provided, so the description carries the burden. It discloses the read-like nature by saying 'Devuelve' but doesn't specify ordering, format, or whether it includes all message types. It adds context (recent messages for specific purposes) but not deep behavioral detail. This is adequate for a simple retrieval tool.

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, front-loaded sentence that efficiently conveys purpose and use cases. No wasted words or redundant information.

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 simple 3-parameter tool with no output schema, the description explains its purpose and why it would be used, complementing sibling tools like opencode_run and opencode_fire. It could mention return structure, but 'recent messages' gives a reasonable expectation. The coverage is concise and adequate.

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 coverage is 100%, with all three parameters described. The description adds no extra parameter-specific semantics beyond the schema; the word 'recentes' loosely relates to the limit parameter but doesn't add syntax or format details. Baseline 3 is appropriate.

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?

Description clearly states it returns recent messages from a session, with a specific verb-resource pair. It distinguishes from siblings like opencode_sessions (which likely lists sessions) and opencode_summarize (which summarizes), and adds scope ('recentes') and intended purposes (continuity, diagnosis, evidence).

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 provides clear usage context: it is meant for continuity, diagnosis, and evidence. It implies when to use the tool, though it does not explicitly name alternatives or exclusion criteria. This matches 'clear context, no exclusions'.

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