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

The description adds real behavioral context beyond the annotations: 'Nothing is sent to the customer' clarifies there is no customer-visible side effect, and the endpoint confirms the operation shape. Annotations already cover the safety profile (idempotent, non-destructive, open-world), so this addition is a meaningful bonus rather than a necessity.

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?

A single tightly-packed sentence plus the endpoint path. The WRITE prefix and assignment action are front-loaded, and no sentence is 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 3-parameter mutation with no output schema, the description covers purpose, effect on the customer, and the alternate identifier inputs. It omits error behavior (e.g. what happens if the target agent is in another department) and whether the conversation's prior assignment is recoverable.

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%, so the baseline is 3, but the description adds genuine value by clarifying that assignee and user_uuid are mutually exclusive ('one of them') — a relationship the JSON schema alone cannot express. The schema still supplies the UUID/email formats, so this is added, not substituted.

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 (WRITE/assign) and resource (conversation) with the exact effect: reassigning to another agent of the same department. It is clearly distinguishable from siblings like textline_resolve_conversation and textline_send_message, which do different things to a conversation.

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?

Gives clear context for use: transferring within the same department, with no customer-facing notification. It does not name alternatives (e.g. resolve_conversation) or state when NOT to use it, so it falls short of the top score despite the useful constraints.

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