restore

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 states that the tool reverses a forget action and makes the memory surface in search again. However, it does not mention potential failure cases, permissions, or whether the operation is idempotent. The description is adequate but minimal.

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 two sentences with no redundant words. The first sentence states the purpose, and the second provides a critical usage hint. It is front-loaded and every sentence earns its place.

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?

The description explains what the tool does and how to get the required parameter. Since there is no output schema, it does not describe return values, but for a simple mutation tool this is acceptable. It could be slightly improved by mentioning confirmation or error behavior.

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?

The input schema covers the single parameter 'id' with a description. The tool description adds value by explaining that the node_id should be obtained from the 'forgotten' tool, providing context beyond the schema's generic description.

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 action ('Restore an archived memory') and the effect ('so it surfaces in search again'). It also explicitly relates to the sibling 'forget' by stating 'This reverses forget', and provides a source for the node_id ('obtain the node_id from forgotten'). This effectively distinguishes it from siblings like forget and forgotten.

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 indicates when to use the tool: to restore an archived memory that was forgotten. It gives a clear prerequisite ('obtain the node_id from forgotten'). However, it does not explicitly state when not to use it or describe alternative tools beyond referencing forget.

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