sage_forget

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

No annotations provided. Description does not specify if deprecation is reversible, what the return value is, or any side effects. For a mutation tool, more behavioral details are needed.

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, front-loaded with the action and resource, no unnecessary words. Highly concise and efficiently structured.

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 no annotations, output schema, and the tool's mutative nature, the description is somewhat lacking in explaining the deprecation process, but is minimally complete for a simple action.

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%, so the description adds limited value. It reiterates 'by ID' and implies reason for deprecation, but does not elaborate on formats or constraints beyond the schema.

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?

Clearly states the action 'deprecate' and resource 'a memory by ID'. Distinguishes from sibling tools like sage_recall or sage_list by focusing on removal of outdated memories.

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?

Explicitly states when to use: 'when a memory is no longer accurate or relevant.' No explicit exclusion or alternatives, but the context of sibling tools implies other tools are for retrieval, not deprecation.

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