create-conversation

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

The description claims that the tool reuses existing conversations for the same set of users, implying idempotent behavior. However, annotations set idempotentHint=false, contradicting the description. This inconsistency undermines transparency.

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, front-loaded with purpose and additional constraint, with no superfluous content.

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?

The description covers the main function and reuse behavior. An output schema exists to document return values. Though permissions are not mentioned, the annotations provide safety hints. The description is sufficiently complete for this tool's complexity.

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 three parameters adequately. The description adds no additional meaning beyond what is in the schema, meriting a baseline score of 3.

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 the tool starts a direct or group conversation and posts an initial message, with explicit mention of reusing existing conversations. The verb 'start' and resource 'conversation' are specific, and the reuse behavior distinguishes it from sibling tools like create-thread.

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 clear context on when to use the tool (starting conversations) and notes the reuse behavior, which guides calling the tool even if a conversation already exists. However, it does not explicitly state when not to use it or provide alternative tools.

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