assign_conversation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'assign' without mentioning whether it overwrites an existing assignment, what permissions are required, or whether a null assignee is possible. This is a significant transparency gap for a mutation tool.

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 a single, front-loaded sentence with no filler or redundancy. It is concise, but the brevity comes at the cost of necessary detail, so it does not earn a perfect score.

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?

Although an output schema exists and may cover return values, the description leaves a critical gap: how to identify the team member. With no annotations, no usage guidance, and a 0% schema coverage, an agent cannot confidently invoke this tool based solely on the description.

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 0%, and the description adds almost no parameter meaning. It does not clarify that `email` or `member_id` is the intended assignee, that one of them should be supplied despite only `conversation_id` being required, or the role of `api_token`. This leaves the agent unsure how to invoke the tool correctly.

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 action and object: 'Assign a conversation to a team member.' It implicitly contrasts with sibling `unassign_conversation`, making the core purpose unambiguous. However, it does not explain how the assignee is specified, which keeps it from being fully specific.

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 use this tool versus alternatives such as `unassign_conversation` or other conversation actions. No prerequisites, such as needing the conversation to be unassigned first, are mentioned.

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