List pending forget proposals awaiting approval on a specified instance. Use this to review and manage memory deletion requests before they take effect.
List pending forget proposals awaiting approval on an instance.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 50) | |
| instanceId | No | Optional instance ID override | |
| memory_name | No | Filter by memory store name |
Changes observed during successful MCP inspections.
v0.23.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full burden. It only states the basic list operation, omitting any behavioral details like read-only nature, authentication requirements, or what happens to proposals after listing. Minimal disclosure.
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 efficient sentence of 8 words, front-loaded with the key action. However, it is almost too minimal and lacks structure for completeness.
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 the 3 parameters and no output schema or annotations, the description is too sparse. It does not clarify what the returned data looks like, nor does it provide context about the approval process. Incomplete for a tool without structural support.
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 schema already documents each parameter. The description adds no extra meaning beyond what is in the schema, earning a baseline score of 3.
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 a specific verb 'List' and clearly identifies the resource 'pending forget proposals' with context 'awaiting approval on an instance'. It effectively distinguishes from siblings like cache_list_pending_proposals and memory_forget.
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 provides no guidance on when to use this tool versus alternatives such as memory_approve_forget or cache_list_pending_proposals. There are no exclusions or context hints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.