append_memory

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

No annotations are provided, so the description must fully disclose behavior. It mentions preserving content and updating timestamp, but fails to address error handling (e.g., non-existent id), permission requirements, size limits, or return value behavior. For a mutation tool, this is insufficient.

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?

Single sentence, front-loaded with the primary action ('Append new markdown'). Every word is meaningful and there is no redundancy or filler.

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 that output schema exists (covering return values) and parameter descriptions are complete, the description is adequate for basic understanding. However, missing behavioral details (errors, prerequisites, side effects) reduce completeness for a mutation tool.

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%, providing baseline 3. The description adds limited semantics beyond the schema: it confirms 'content' is Markdown and specifies appending to the end. However, this is largely redundant with schema field descriptions.

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 indicates the action (append), the resource (existing memory), and the effect (preserve content, update timestamp). It distinguishes from siblings like 'update_memory' which would replace content, and 'create_memory' which creates new.

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 implies when to use (to add content without replacing), but lacks explicit when-not-to-use or alternatives. The sibling tool 'update_memory' provides implicit contrast, but no direct comparison is given.

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