memory_reflect

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

The description explicitly includes 'forget' as a core action, which is a destructive memory operation, yet the annotations declare destructiveHint: false. This is a direct contradiction between the described behavior and the structured metadata. Beyond that, the description adds little behavioral context that the annotations do not already cover or contradict.

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 a single dense sentence that front-loads the action list and then supplies the usage triggers. It contains no filler, no repetition of schema content, and every clause contributes useful selection information.

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 tool with four parameters and six distinct actions, the description plus full schema coverage is mostly sufficient. It explains when to use the tool and what actions are available. The main gap is not explaining the semantics of 'link' or 'pin' beyond their names, but the schema descriptions fill in the parameter mechanics.

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 100%, so the baseline is 3. The description itself does not add parameter-level detail, but the schema already explains text, target, agent, and action sufficiently. No additional semantic explanation is required.

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 opens with a concrete list of actions and the resource they act on: 'Add, update (supersede), forget, link, or pin your memories.' This immediately identifies the tool's scope and distinguishes it from sibling tools like memory_add, which only handles adding.

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 gives explicit triggering conditions: 'Use when you notice a contradiction, finish a task, learn a durable preference that should persist, or the user declares something permanent.' This is clear context for when to invoke the tool, though it does not explicitly mention when not to use it or name alternatives.

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