get_team_unassigned_conversations

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

With no annotations, the description carries the full burden, and it does add real value by disclosing the required permission scope and the underlying endpoint. It still omits the return shape, whether pagination metadata is included, and any rate-limit or ordering behavior beyond what 'Get' implies.

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 body is short and front-loaded with the core definition, but the first line merely restates the tool name and the trailing 'GET /api/v1/...' and 'Tags: Conversations' lines are generated boilerplate that adds little for an agent. A portion of the text does not earn its place.

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 six-parameter read tool with no annotations and no output schema, the description covers purpose and auth but says nothing about result contents or how the rich filter/sort parameters shape output. It is adequate but leaves the agent guessing about return values and sibling overlap.

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%, including detailed filter operators, filterable fields, and sort enums, so the baseline is 3. The description adds no parameter meaning beyond the schema — it never mentions filtering, sorting, or page size, all of which are central to this endpoint.

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 and resource with a precise scope: conversations assigned to a team but with no assigned agent. The required team `id` parameter reinforces the team-scoped nature. It does not explicitly distinguish itself from the sibling `get_unassigned_conversations`, so an agent must infer the difference from the name alone.

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?

Usage is only implied by the phrase 'assigned to team but not assigned to any agent' and the stated `conversations:read_team_inbox` permission prerequisite. There is no explicit statement of when to choose this over `get_unassigned_conversations`, `get_assigned_conversations`, or `get_all_conversations`, leaving the agent to infer the routing.

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