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

Annotations only supply destructiveHint=true, so the description's claim that the action is 'reversible by reassigning' is genuinely additive context that softens the destructive flag without contradicting it. It does not, however, say what happens to the previous assignee, whether notifications fire, or what permissions are required.

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?

Two tight sentences plus the underlying endpoint; the core action is front-loaded and no sentence is filler. The API path is arguably extra but is short and useful for mapping to Trengo's REST surface.

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 five-parameter mutation with no output schema and only a destructiveHint annotation, the description covers the essentials: what changes, the two assignment modes, the optional note, and reversibility. Missing only side-effect detail such as notifications or prior-assignee handling.

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%, including the conditional 'required when type is team/user' notes, so the schema carries the parameter burden. The description only restates that the note is optional and that the target may be a user or team, adding nothing beyond what the schema already says.

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?

Specific verb ('assign') plus resource ('ticket') with the target dimension named (user or team) and the optional note acknowledged. It is clearly distinct from siblings like trengo_close_ticket or trengo_reopen_ticket, though it never names an alternative to contrast against.

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?

Usage is implied by the verb and by the 'reversible by reassigning' hint, but there is no explicit guidance on when to assign versus closing, updating, or replying to a ticket, and no stated prerequisites such as needing to resolve a user_id/team_id first.

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