remove_team_assignee

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 naming the required `conversations:update_team_assignee` permission and the exact endpoint. However, it says nothing about mutation behavior: whether removal is idempotent, what happens if the team is not assigned, or whether removing the last team assignee affects routing.

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 text is short and front-loads the action, but the title line merely restates the tool name and the 'Tags: Conversations' line contributes little for an agent. The permission requirement is the most valuable sentence and is placed well.

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 single-parameter mutation with no annotations and no output schema, the description covers permission and endpoint but leaves failure modes and post-removal state unaddressed. It is minimally adequate rather than complete.

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?

Only one parameter exists and the schema documents it fully as a path parameter with 100% coverage. The endpoint path clarifies that `uuid` is a conversation UUID, which adds modest meaning beyond the bare schema, but no format or sourcing guidance is provided.

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 heading 'Remove Team Assignee' plus the endpoint PUT /api/v1/conversations/{uuid}/assignee/team/remove makes it clear this strips a team assignment from a specific conversation. The verb and resource are specific, though the description never explicitly contrasts this with remove_user_assignee or update_team_assignee.

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?

There is no guidance on when to call this versus remove_user_assignee or update_team_assignee. The only contextual constraint given is the required permission scope, which is a prerequisite rather than usage direction.

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