Delete TraeCN Conversation

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds valuable context: the deletion is permanent with no recovery, and it requires an explicit acknowledgement. It explains the consequence beyond the mere flag and reinforces the need for care, which adds behavioral transparency beyond 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?

Two sentences with zero redundant words. The primary purpose is front-loaded, followed by the required preconditions and consequence. Efficient and well-structured.

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 destructive operation with three required parameters and an existing output schema, the description covers the essential aspects: what it does, what inputs are needed, and the irreversible consequence. It does not describe the response format, but the output schema likely handles that. Minor gap: no mention of what happens if the conversation is active (the description says 'inactive' but doesn't specify behavior for active ones), though the acknowledgement implicitly addresses deletion of inactive ones. Overall adequate.

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 coverage is 100%, so the baseline is 3. The description restates the source of expectedTitle (from traecn_list_conversations), which reinforces the schema, but does not add new semantic meaning beyond what the parameter descriptions already provide. No extra context about format, timing, or side effects.

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 verb ('delete'), a clear resource ('inactive TraeCN conversation'), and a precise identifier mechanism ('by stable identifier'). It distinguishes from siblings like traecn_select_conversation and traecn_create_conversation, and adds qualifiers ('permanently', 'inactive') that make the purpose unambiguous.

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?

It clearly specifies the required inputs (exact expectedTitle from traecn_list_conversations and an acknowledgement) and highlights the irreversible nature with 'no gateway recovery path.' It does not explicitly contrast with alternatives, but the conditionality is clear. Slight deduction for not stating a 'when not to use' scenario.

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