get_unassigned_conversations

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic functionality and HTTP endpoint, but does not mention that it is a read-only operation, any side effects, auth requirements, or rate limits. The GET method hints at non-destructiveness, but it is not explicit.

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 appropriately sized with two core sentences. The purpose is front-loaded in the second line. However, the first line is a redundant restatement of the tool name, which is minor waste. Overall efficient.

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 the low complexity (2 parameters, no output schema, no nested objects) and no annotations, the description adequately covers the core purpose and includes the HTTP endpoint. It does not mention pagination behavior explicitly, but the schema covers parameter details. Comprehensive enough for an agent to select and invoke the tool.

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 the input schema already documents both parameters (page and page_size) with defaults and limits. The description adds no additional meaning about the parameters, meeting the baseline expectation.

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 verb 'Get' and the resource 'conversations' with a specific scope 'not assigned to any user and team'. Among siblings like get_assigned_conversations and get_all_conversations, this description uniquely identifies what the tool does.

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 usage for retrieving unassigned conversations, but it does not explicitly state when to use this tool over alternatives like get_assigned_conversations or get_team_unassigned_conversations. No exclusions or context are provided.

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