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

Annotations already declare this is a non-read-only, non-destructive, open-world write, so the safety profile is covered. The description adds that the ticket carries a number, subject and priority, and that the note is private to the team, but says nothing about permissions, whether the originating conversation is modified, or what is returned. It is also silent on idempotent retry behavior beyond what the schema already documents.

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 sentences, front-loaded with the core action and resource, no repetition. The clause 'so it stops living only in the inbox' is motivational flavor rather than actionable detail, but it is short enough not to be a real cost.

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 plus the annotation block covers the essentials: what is created, the notable fields, and the safety profile. The gaps — required conversationId semantics, priority levels, and the fact that 'number' is a result rather than an input — are modest but real.

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 40%: only note and idempotencyKey are documented, and the description reinforces the note's private-to-team nature. It names subject and priority, which partially compensates, but the required conversationId has no description in either place, and 'number' is mentioned as if it were an input when it appears to be a generated value.

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?

The description states a specific verb and resource ('Promote a conversation to a support ticket') plus the fields it carries, so an agent can distinguish it from generic creation tools like create_post or create_contact. It does not name a sibling it is not, so it stops short of full differentiation.

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 'promote a conversation to a support ticket' — you use it when an inbox conversation needs to become tracked work. There is no explicit when-not guidance and no routing away from the closely related sibling add_conversation_note, which is a plausible alternative when the agent only wants to annotate a thread.

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