Remember-Memory

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool 'removes' (implying a destructive operation) but doesn't clarify if removal is permanent, reversible, requires specific permissions, or has side effects. The mention of 'specific memory within a specified category' adds some context about scope, but critical behavioral traits are missing.

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 that directly states the tool's purpose. There's no wasted language, and it's appropriately sized for a basic tool description.

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 destructive operation with 3 undocumented parameters and no annotations or output schema, the description is inadequate. It doesn't explain what constitutes a 'memory', how categories work, what 'is_global' means, or what happens after removal. The agent would struggle to use this tool correctly without additional context.

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 0%, so all 3 parameters are undocumented in the schema. The description only vaguely references 'category' and 'specific memory' (implied by 'memory_content'), leaving 'is_global' completely unexplained. It adds minimal meaning beyond the parameter names themselves.

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 verb 'removes' and the resource 'specific memory within a specified category', making the purpose understandable. It distinguishes from sibling 'remove_memory_category' by targeting individual memories rather than entire categories, but doesn't explicitly contrast with 'remember_memory' or 'retrieve_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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention when to choose this over 'remove_memory_category' (for deleting entire categories) or how it relates to 'remember_memory' (for adding memories) and 'retrieve_memories' (for viewing).

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