get_unanswered_conversations

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

No annotations are provided, so the description carries the full burden. It only states what the tool shows, with no mention of side effects, read-only nature, sorting, pagination, or other behavioral traits. The agent gets no insight into how the tool behaves beyond its purpose.

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 that front-loads the core purpose. It is efficient with no wasted words. However, it could be slightly more structured (e.g., separating the query tag) but remains concise and clear.

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 tool with 13 parameters and no output schema or annotations, the description is minimal. It does not explain the return format, pagination behavior, how 'query' interacts with other filters, or what the default sorting is. Significant gaps remain for an agent to use it correctly.

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 input schema has 100% coverage with descriptions for all 13 parameters, so the baseline is 3. The description adds no extra meaning beyond the schema; it only echoes the tool's purpose. No additional context is provided for parameters like 'query' or 'hours'.

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 it shows conversations where the last message is from the client (unanswered), using a specific verb ('Muestra') and resource ('conversaciones sin responder'). It effectively distinguishes itself from sibling tools like 'get_recent_conversations' or 'search_conversations' by focusing on the unanswered criterion.

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 no guidance on when to use this tool versus alternatives. It includes a '[query]' hint but does not explain the context or when to prefer this over other conversation retrieval tools. No explicit exclusions or alternative names are given.

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