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

Annotations already declare a non-read-only, non-idempotent mutation, and the description adds real context beyond that: it discloses the status transition (pending or escalated to active) and the transcript side effect of a system line. It still omits permission requirements and any notification side effects.

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?

Three short sentences with the purpose front-loaded and the two body variants stated compactly. The inline JSON notation is slightly dense but earns its place by disambiguating assign versus unassign.

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 two-parameter mutation with no output schema, the description covers the action, the payload variants, and the resulting state and transcript effects. Only permission/auth expectations and whether the caller is notified are missing.

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 coverage is 100% and already documents both id and assigned_to including the null-to-unassign case, so the description largely restates the schema. It confirms the body shape but adds no format or constraint details the schema lacks.

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?

States a specific verb pair and resource ('Assign or unassign a conversation') and covers both directions in one tool. It does not name a sibling such as update_conversation to distinguish scope, so it stops short of a 5.

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?

The body examples implicitly tell the agent how to choose assign versus unassign, and the note that it moves pending/escalated conversations to active hints at applicable states. There is no explicit guidance on when to use this instead of update_conversation or other conversation tools.

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