get_recent_conversations

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

With no annotations, the description only states basic behavior (retrieving recent conversations sorted by last activity). It omits side effects, authentication needs, rate limits, pagination details, or what the response contains. The ambiguous '[query]' at the end adds confusion.

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 concise (one short sentence) but includes an unclear '[query]' fragment. It lacks structure and does not front-load the most critical 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?

Given 13 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain the meaning of many parameters (e.g., agent_id, message, format), pagination behavior, or response format. The tool is complex but the description provides minimal context.

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% (all 13 parameters have descriptions). The description adds little beyond the schema, except possibly implying the sorting behavior. Baseline score of 3 is appropriate as 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?

The description clearly states the tool retrieves recent conversations ordered by last activity. The verb 'Obtiene' and resource 'conversaciones mas recientes' align with the name. However, it does not differentiate from sibling tools like search_conversations or get_conversations_by_agent.

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 lacks any guidance on when to use this tool versus alternatives. No mention of prerequisites, context, or exclusions is provided.

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