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

Annotations already indicate this is a mutating operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that it creates a support ticket from the conversation context, providing a useful behavioral detail. However, it does not go deeper into prerequisites or side effects beyond that.

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 concise sentences with no fluff. The first states the core action, and the second specifies the behavioral outcome, making it highly efficient and well-structured.

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 simple escalation action, the description is sufficient: it names the platforms, the input conversation, and the ticket creation. It does not mention preconditions like connector connectivity or return values, but the schema and annotations cover the essential details, making it reasonably 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 descriptions cover 3 of 4 parameters (note, conversationId, targetConnector), and the description clarifies that the escalation uses conversation context. The priority parameter lacks a description but is self-explanatory via its enum. The description adds marginal value beyond the schema.

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 uses a specific verb ('escalate') with a clear resource ('social conversation') and destination ('connected support platform'), and explicitly states the ticket-creation outcome. This distinguishes it from siblings like reply_to_conversation or list_conversations.

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 clearly implies the use case: when a social conversation needs to be escalated to an external support platform. It does not explicitly name alternatives or exclude other tools, but the context is clear enough given the sibling list.

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