get_conversation

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

No annotations are present, so the description carries the full behavioral burden. It does disclose the ordering behavior and that only the N most recent messages are returned. However, it does not mention error behavior, authentication, or explicitly confirm that the operation is read-only beyond the verb 'Obtiene'.

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 sentence with a parenthetical ordering clarification. Purpose is front-loaded and there is no filler. Every element contributes useful 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 low-complexity getter with one required parameter and one optional parameter with a default, the description covers what is returned and the ordering. The explicit 'messages[0] = más reciente' hint mitigates the lack of an output schema. Minor gaps like empty-conversation behavior or size limits are not fatal for invocation.

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 50%: 'size' is described but 'conversation_id' is not. The description maps 'N' to the size parameter and 'una conversación' to conversation_id, adding mild semantic value. It does not provide ID format, constraints, or behavior when size exceeds available messages.

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 states a specific verb ('Obtiene'), the target resource ('los N mensajes más recientes de una conversación'), and the ordering. This clearly distinguishes it from sibling tools like list_conversations, which would list conversations rather than messages. It is not a tautology and provides concrete scope.

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 implies the tool is for reading recent messages of a single conversation, but it never explicitly says when to prefer it over alternatives or when not to use it. No exclusions or sibling comparisons are provided. Usage context is inferable from 'de una conversación' but is not made actionable.

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