get_team_unassigned_conversations

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

With no annotations provided, the description carries the full burden. It states it's a GET endpoint and explains the filtering logic, which is a basic read operation. However, it does not disclose authentication requirements, rate limits, or any side effects. This is acceptable for a simple retrieval tool but lacks depth.

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 short and to the point, consisting of two sentences plus the endpoint path and tag. However, the first sentence repeats the tool name, which is slightly redundant. Overall, it is efficient but could be more streamlined.

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 simplicity of the tool (list retrieval with pagination, no output schema), the description provides enough context to understand the core functionality. It adequately explains what the tool returns (unassigned conversations for a specific team). The schema covers pagination details, so no further explanation is needed.

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 covers all three parameters with descriptions, achieving 100% coverage. The tool description does not add extra meaning beyond what the schema provides; it only implicitly references the 'id' parameter. Baseline score of 3 is appropriate.

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 identifies the tool as retrieving conversations that are assigned to a team but not to any agent. The verb 'Get' and resource 'Team Unassigned Conversations' are specific and distinguish it from siblings like get_unassigned_conversations and get_assigned_conversations.

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 usage context—fetching unassigned conversations filtered by team—but does not explicitly advise when to use this tool versus alternatives like get_unassigned_conversations or get_assigned_conversations. No exclusions or prerequisites are mentioned.

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