append_memory

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

With no annotations, the description carries the full load and does disclose non-obvious effects: content is joined with a timestamp separator and history is tracked, so an agent knows the appended text is not stored verbatim as a standalone blob. It omits failure behavior for an invalid memory_id and whether appends are atomic or idempotent.

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?

Front-loaded with the core semantics in two sentences, then an Args block that repeats the parameters with added meaning. The Args section is somewhat redundant with the schema but earns its place because the schema has no descriptions.

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?

An output schema exists, so return values need not be explained, and the description covers what an annotion-free mutation tool most needs: the shape of the appended content, history tracking, and the source default. Only the error case (memory_id not found) is left unaddressed.

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 description coverage is 0%, so the description must compensate, and it does: all three parameters are explained with meaning beyond their titles (content is timestamp-appended, source defaults to the connected client's name). Minor inconsistency: the schema shows source default as empty string while the description says the client name.

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?

States a specific verb and resource ("Append additional context to an existing memory") and adds the operative distinction "without replacing it", which separates it from save_memory/update_memory in spirit. It stops short of naming the sibling it replaces, so an agent must infer that update_memory is the replacement path.

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?

Clear situational context: use this when you want to add to an existing memory rather than overwrite it, and memory_id + content are required so the precondition (memory must exist) is implied. No explicit "when not to use" or named alternative tool, which keeps it below a 5.

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