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

Annotations only supply destructiveHint=true; the description adds genuinely useful behavioral context by stating the operation is reversible via reassignment and that it targets either a user or a team. It stops short of covering auth requirements, whether the assignee is notified, or what the response contains, so it is strong but not exhaustive.

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 that are front-loaded with the core action, then reversibility, then the API endpoint. No filler, and nothing important is buried.

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, the description covers purpose, target selection, the optional note, and reversibility. It omits prerequisites for sourcing the user/team IDs and any note on side effects such as notifications, which keeps it just under fully complete.

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% and the schema already documents the type enum and the conditional requirement that team_id is needed for type=team and user_id for type=user. The description restates the user/team choice and the optional note, adding no format or syntax detail beyond the schema, so the baseline 3 applies.

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 (assign) plus the resource (ticket) and the two target kinds (user or team), plus an optional note. An agent can distinguish this from siblings like trengo_close_ticket, trengo_reopen_ticket, or trengo_send_ticket_message without opening any schema.

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 — assigning when a ticket needs an owner — but there is no explicit when-to-use guidance, no mention that user_id/team_id must first be obtained from trengo_list_users or trengo_list_teams, and no exclusion of related siblings.

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