List TraeCN Conversations

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value beyond these by stating that the output identifiers are 'stable' and 'accepted by conversation-scoped tools,' which informs the agent about output usability. There is 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 a single, tight sentence that front-loads the primary intent ('List the conversations') and packs in the scope, identifier property, and read-only nature. Every word earns its place; there is no fluff or redundancy.

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?

Given the tool's simplicity (no params, no side effects), the description covers the essential behavior: what it lists and why the identifiers matter. An output schema exists, so the description need not detail return fields. It could have mentioned that it reflects the 'current mode' but it does, so the context is sufficiently complete for an agent to use the tool 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?

The tool has zero parameters, and schema description coverage is 100% (vacuous). Baseline for 0 params is 4. The description adds no parameter-specific semantics because none exist, but it does not need to. The absence of parameters is implicitly clear from the empty schema, and the description's mention of 'conversations available in the current TraeCN mode' reinforces what the output will contain.

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 action ('List the conversations'), the scope ('in the current TraeCN mode'), and the key feature ('stable identifiers accepted by conversation-scoped tools'). This distinguishes it from siblings like traecn_create_conversation or traecn_select_conversation, which perform different operations. The verb, resource, and differentiation are all explicit.

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 gives a clear usage context: 'call when choosing or verifying conversation context.' It implies this tool is for selecting or confirming conversations before using conversation-scoped tools. It does not explicitly name alternatives or state when not to use it, but the phrase 'choosing or verifying' provides sufficient guidance for an agent to decide when to invoke it over create/delete/select.

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