create_conversation_entry

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that entries are 'formatted with metadata for easy filtering' and that they become 'searchable via search_archival_memory,' which adds useful context about the tool's behavior. However, it doesn't disclose important behavioral traits like whether this is a write operation (implied but not stated), what permissions are needed, or how the data is stored/persisted.

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 efficiently structured in two sentences that each earn their place: the first states the core purpose and use case, the second explains the formatting benefit. There's no wasted text, and the most important information (what the tool does) is front-loaded.

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 write operation with 6 parameters and no annotations or output schema, the description provides adequate but minimal context. It covers the basic purpose and relationship to search_archival_memory, but doesn't address important contextual aspects like error conditions, data validation, or what happens on successful creation. The lack of output schema means the description should ideally mention what the tool returns.

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?

With 100% schema description coverage, the schema already documents all 6 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema descriptions. It mentions metadata formatting generally but doesn't explain how specific parameters like source or session_id affect this formatting.

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 specific action ('Store a conversation entry') and resource ('in an agent's archival memory'), distinguishing it from sibling tools like search_archival_memory (which searches) or create_memory_block (which creates different memory types). It explicitly mentions the tool's purpose for recording conversations from external sources.

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 for when to use this tool ('to record conversations from external sources like Claude Code sessions that should be searchable via search_archival_memory'), giving a specific use case and mentioning the related search tool. However, it doesn't explicitly state when NOT to use it or compare it to similar tools like create_memory_block or attach_memory_block.

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