Conversation Assignment: Assign Conversation

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

Annotations already declare mutating (readOnlyHint=false), non-idempotent, non-destructive, open-world behavior. The description usefully adds the auth requirement (User API key header) and language/digit handling context, but does not say what a reassignment replaces, whether the prior assignee is notified, or permission requirements.

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 core purpose is front-loaded, followed by endpoint, auth, and param notes in a compact block. It is somewhat dense (mixing endpoint/auth/body/language into one paragraph) but no sentence is truly wasted.

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 mutation tool with no output schema, the description covers endpoint, auth, body fields, and passthrough but omits success/return behavior and side effects. Adequate to invoke but incomplete on outcome expectations.

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 baseline is 3. The description restates body fields (assignee_id, team_id) and the extra_body passthrough that the schema already documents in detail, adding little beyond the schema.

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 ("Assign a conversation to an agent or a team") and even includes the exact REST endpoint, making scope unambiguous. It distinguishes itself clearly from siblings like create_conversation or toggle_conversation_status.

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?

It never says when to use this tool versus alternatives, nor does it state prerequisites or exclusions. The only conditional behavior (team_id ignored when assignee_id is present) is in the schema, not framed as guidance in the description.

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