forget

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

No annotations are provided, so the description must disclose behavior. It states 'Delete', which implies mutation and potential irreversibility, but does not discuss permissions, effects on linked data, or error states. For a simple delete, it provides basic transparency but could be more detailed.

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 extremely concise, with three short sentences that front-load the purpose. Every sentence adds value, and there is no redundancy or extraneous text.

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 a single required parameter and no nested objects, the description covers the core functionality. However, it does not mention the output or return value (despite an output schema existing), nor address error handling or idempotency. Basic completeness is achieved but not enhanced.

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 has 0% description coverage for 'memory_id', but the tool description explains the parameter as 'The id of the memory to remove', adding meaning beyond the schema's type and title. This compensates well for the schema gap.

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 'Delete a memory by its id', using a specific verb and resource. Among siblings like 'remember' (create) and 'recall' (retrieve), this tool's purpose is distinct and unambiguous.

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 explicitly says 'Use this when a stored fact turns out to be wrong or outdated', providing clear when-to-use guidance. It does not mention when not to use or alternatives, but the direct context is sufficient for an agent.

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