Leer una conversación

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds one genuine behavioral detail beyond that: messages are returned "en orden" (ordered). It does not disclose limits, pagination, or whether all messages or only a recent window are returned.

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?

A single front-loaded sentence with the resource and the ordering guarantee; nothing is wasted. The bracketed tag partially duplicates what the annotations already declare (read-only, classroom scope), which is a small redundancy rather than a real defect.

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 two-parameter read tool with full schema coverage and annotations carrying the safety profile, the description is nearly complete. The remaining gap is minor: no mention of result size, pagination, or whether an empty thread returns an empty list.

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 both parameters (thread_id = "Conversación", classroom_id = "Aula") are already documented in the schema. The description confirms the scope is a conversation within a classroom but adds no syntax, format, or constraint detail beyond the schema, so the baseline 3 applies.

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: "Devuelve los mensajes de una conversación del aula". This is clearly a single-thread read, distinguishable from list_waiting_chats (which surfaces pending conversations) and reply_chat (which writes). It does not explicitly name those siblings, which keeps it from 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?

Usage is only implied: the required classroom_id/thread_id signal that this is a per-thread retrieval, and the "solo lectura" tag signals read-only intent. There is no explicit statement about when to prefer this over list_waiting_chats, nor that a thread_id must first be obtained from that listing tool.

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