Update a memory

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

Discloses that it 're-stamps it as updated and refreshes its index line', but with no annotations, it lacks details on idempotency, permissions, or whether omitted fields are unchanged. Additional behavioral context would be beneficial.

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?

Two sentences with no redundancy. The core purpose and a usage hint are front-loaded, making it efficient.

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?

Despite having 4 parameters, no output schema, and no annotations, the description does not explain what each parameter does, how update behavior affects omitted fields, or what the response looks like. The sibling tools indicate a rich set of memory operations, so more detail is warranted.

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%, and the description provides no explanation for any of the 4 parameters (body, name, type, description). The agent must infer meaning from names alone, which is insufficient.

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 uses the specific verb 'Edit' and resource 'existing memory', clearly distinguishing from siblings like memory_remember (create) and memory_forget (delete).

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?

Provides explicit guidance: 'Prefer this over creating a near-duplicate.' This tells the agent when to use this tool instead of creating a new memory, but does not mention other alternatives or exclusion cases.

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