update_team_assignee

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the required `conversations:update_team_assignee` permission, but says nothing about side effects (does it clear an existing user or team assignee?), idempotency, or what is returned on success or failure. For a mutation with zero annotation coverage, this is a meaningful gap.

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, but a large share is low-value boilerplate: the title repeated as the first line, a permission string, a raw HTTP route, and a redundant 'Tags: Conversations' line. Useful content (permission requirement, endpoint) is not front-loaded relative to the noise.

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?

This is a mutation endpoint with no annotations and no output schema, so the description should explain the effect of the assignment and any replacement/override semantics. It supplies only the permission and route, leaving the agent unable to predict the operation's effect on existing assignments.

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 both parameters (uuid path parameter and assignee_id team ID) are already documented. The description adds no format, constraint, or sourcing detail beyond the schema, so the baseline 3 applies.

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 opens with the title restated verbatim ('Update Team Assignee'), and the only added information is the HTTP route PUT /api/v1/conversations/{uuid}/assignee/team plus a tag line. This implies assigning a team to a conversation, but the agent learns that mostly from the parameter names, not from an explicit statement of what the tool does. It does not distinguish itself from siblings such as update_user_assignee or remove_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?

No guidance on when to use this tool, when to prefer update_user_assignee instead, or whether this replaces an existing user assignee. The only stated precondition is the required permission, which is a prerequisite rather than usage guidance.

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