Create Message in Conversation

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true. The description adds that messages reach customers externally or stay as internal notes, which is real behavioral context, but it never warns that retries may duplicate messages (non-idempotent) and does not disclose permission requirements or whether a sent message can later be edited or deleted.

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?

The purpose sentence is front-loaded and the Args/Returns/Examples structure is easy to scan. There is some redundancy since the Args block repeats schema descriptions verbatim, costing lines without adding information.

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?

With no output schema, the description helpfully includes a Returns line covering the created message ID and confirmation, and it covers every input with examples. Remaining gaps are edge behavior: error cases (e.g., nonexistent conversation_id) and whether the account/conversation must be accessible to the caller's token.

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 all five parameters are already documented in the schema, including the message_type enum and the private flag. The description's Args block largely restates those same definitions; the only added value is the paired worked examples, which is baseline-level supplementation.

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 ("Create a new message in a Chatwoot conversation") plus the key subtype distinction (outgoing customer message vs. private internal note). This clearly separates it from the read-oriented siblings such as chatwoot_list_messages and chatwoot_get_conversation.

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?

"This tool sends a message in an existing conversation" establishes the precondition and the two usage modes, and the two examples make the outgoing-vs-private-note choice concrete. It never states when not to use it (e.g., use chatwoot_list_messages to read existing messages instead), so it falls short of explicit alternatives.

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