Create Message in Conversation

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

Annotations indicate readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds meaningful behavioral context: it specifies the message can be outgoing or incoming, private or public, and explicitly states the return value includes created message details. No contradiction with annotations.

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 description is well-structured with clear sections (Args, Returns, Examples). Every sentence earns its place, and the examples are concise yet illustrative. No fluff or repetition of what the schema already conveys.

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?

Despite lacking an output schema, the description explicitly states what the tool returns. It covers the main use cases (public reply, internal note) and explains defaults. Given the tool's complexity (4 params, two required), this is complete enough for an agent to use it correctly.

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 covers all 4 parameters (100% coverage), so baseline is 3. The description adds value by restating parameters in a compact Args section, clarifying default values for message_type and private, and providing two concrete examples that demonstrate parameter usage and practical intent.

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 clearly states "Create a new message in a Chatwoot conversation." It uses a specific verb ('create') and resource ('message'), and naturally distinguishes from sibling tools that list, get, or filter conversations/messages.

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 provides practical guidance with examples for both public replies and private internal notes, clarifying when each mode is appropriate. However, it does not explicitly mention alternatives or when not to use this tool (e.g., 'for reading messages use chatwoot_list_messages'), though the context makes it obvious.

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