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

Annotations only supply destructiveHint=true, so the description carries most of the load, and it delivers the key non-obvious behavior: no customer-facing message is sent as a side effect of creation. It stops short of covering failure modes, duplicate-ticket behavior, or required permissions. The creation framing is not a genuine contradiction of destructiveHint, which here plausibly signals state mutation rather than data loss.

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 short sentences, front-loaded with the core action and immediately followed by the single most decision-relevant side-effect fact. No filler or restated title text.

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 three-parameter creation tool with no output schema, the description covers the action, the prerequisite (existing contact), the channel scoping, and the absence of automatic customer notification. What is missing is only ancillary: error behavior and whether duplicate tickets are permitted.

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 channel_id and contact_id are already documented, and the description adds only the requirement that the contact already exist. It adds no syntax, format, or optionality guidance beyond the schema's baseline.

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 and resource ('Open a new ticket') plus a binding constraint ('for an existing contact on a channel'), which separates it from sibling creation tools like trengo_create_contact and trengo_create_board_card. The API endpoint reference reinforces what the call does.

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 description gives a clear workflow cue: creating a ticket alone does not notify the customer, and trengo_send_ticket_message is required to do so. That effectively tells the agent when this tool is a preliminary step, though it never states when to prefer a different ticket tool or what happens if the contact or channel is invalid.

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