Create TraeCN Conversation

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

Annotations already indicate non-read-only and non-idempotent, but the description adds clarity by stating that each call creates a new conversation and sets it as the active target. This is a useful behavioral disclosure beyond the annotations, without contradicting them, though it doesn't cover output format or failure modes.

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?

Three sentences, each serving a distinct purpose: the primary action, a usage caveat, and the return value. Front-loaded with the core purpose, no wasted words, and easy to scan.

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 zero-parameter tool with an output schema, the description covers everything needed: the action, side-effect, usage policy, and return information. An agent has all necessary information to invoke it correctly without further clarification.

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?

The tool has zero parameters, so schema coverage is 100% and there is nothing to explain. Baseline of 4 applies, and the description does not need to compensate for any missing parameter details.

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 states a specific action ('create') and resource ('TraeCN conversation') and distinguishes it from siblings like select_conversation and list_conversations by focusing on creation and the 'active target' side-effect. It is immediately clear what the tool does and how it differs from similar tools.

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?

Explicitly warns that every call creates an additional conversation and advises calling at most once per genuinely new context, which is strong usage guidance. It does not explicitly name alternatives, but the context implies when to use this versus selecting an existing conversation, leaving a small gap in exclusion guidance.

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