mem0-mcp-selfhosted

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 reveals the cascading deletion effect (which is critical for a destructive operation) and notes functional equivalence to another tool in specific contexts. However, it lacks details on permissions required, error conditions, confirmation prompts, or rate limits—important for a deletion tool. The description doesn't contradict annotations (none exist), but it's incomplete for a destructive operation.

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 brief and front-loaded with the core purpose in the first sentence. The second sentence adds context but is arguably necessary to clarify the tool's scope. There's minimal waste, though it could be more structured (e.g., separating usage notes). It's appropriately sized for a tool with clear parameters and annotations.

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 tool's complexity (destructive deletion with cascading effects), no annotations, and an output schema (which handles return values), the description is moderately complete. It covers the main action and a key behavioral trait (cascading), but lacks safety warnings, error handling, or examples. For a deletion tool, this is a significant gap, though the output schema mitigates some completeness needs.

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%, with each parameter well-documented in the schema (e.g., 'User entity to delete (cascades to all memories)'). The description adds no parameter-specific information beyond what's in the schema. According to scoring rules, with high schema coverage (>80%), the baseline is 3 even without param info in the description, which applies here.

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 tool's purpose: 'Delete an entity and cascade-delete all its memories.' This specifies the verb (delete), resource (entity), and scope (with cascading effect). However, it doesn't explicitly distinguish this tool from sibling 'delete_all_memories' beyond noting functional equivalence in self-hosted mode, which is more about behavioral transparency than purpose differentiation.

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 like 'delete_all_memories' or 'delete_memory' from the sibling list. The mention of functional equivalence to 'delete_all_memories' in self-hosted mode is a behavioral note, not usage guidance. There's no indication of prerequisites, constraints, or typical scenarios for invoking this tool.

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