add_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. It discloses validation/sanitization and the persistence/indexing behavior of the four metadata fields, which is useful. It does not mention the return value, whether the tool can duplicate conversations, or any side effects or failure modes beyond validation.

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 compact and readable, front-loading the core action and then explaining the metadata fields. The formatting is clean, though the trailing phrase about external imports is slightly tangential and could be trimmed.

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 7-parameter write operation with no annotations and no parameter descriptions in the schema, the description is under-equipped. It explains why the four universal fields exist and the indexing behavior, but it does not clarify return values, error conditions, or the meaning of date/title/content. The presence of an output schema helps, but the description still leaves significant gaps.

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 input schema lists 7 parameters but none of them have descriptions, and the description adds meaning only for session_id, user_id, tags, and conversation_type by explaining they are persisted and indexed. date, title, and content receive no semantic explanation beyond their names and types, which is a notable gap given the 0% schema description coverage.

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 adds a new conversation to the memory system, and it names the universal metadata fields. However, it does not explicitly contrast itself with the update_conversation sibling, which is an easy distinction to miss in an agent's selection process.

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 explains that the optional fields can be used for metadata search and that they may originate from external imports, which implies when these fields matter. It does not spell out when to prefer add_conversation over update_conversation or when certain metadata fields are required, leaving usage context implicit.

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