create_conversation

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

With no annotations at all, the description carries the full burden, and what it contributes is useful but thin: the required scope and the HTTP endpoint. It does not disclose the consequential behavior an agent needs before calling a 17-parameter mutation — that an actual outbound message may be dispatched, that a contact may be created or updated, or that automation rules fire conditionally on the `initiator` value.

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?

It is short and front-loaded, so there is little waste in length, but the four lines are mostly metadata scaffolding: the tag line and the raw endpoint path consume space that could have carried behavioral substance. Brevity here reflects under-specification rather than disciplined economy.

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 high-complexity, 17-parameter, side-effecting tool with no annotations and no output schema, the description is far too thin. An agent cannot learn from it what the call actually produces or triggers, and must reconstruct that entirely from parameter docs.

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 the schema already documents all 17 parameters including the nuanced `initiator` and `reuse_contact` semantics. The description adds nothing about parameters beyond what the schema states, so the baseline 3 applies.

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 only purpose statement is "Create Conversation", which is a verbatim restatement of the tool name and title. The POST path and tag add no semantic insight into what a created conversation actually contains (an initial message plus a possibly new/matched contact), and nothing distinguishes it from siblings like create_contact or create_contact_note.

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?

There is no guidance on when to use this versus alternatives, nor any exclusions. The `conversations:write` permission note is a prerequisite, not usage guidance, and the absence of a stated condition for when a new conversation should be created leaves the agent to infer everything from the schema.

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