MCP Memory SQLite

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

No annotations are provided, so the description must carry full disclosure burden for this destructive operation. It fails to mention whether deletion is permanent, if it cascades to related entities, required permissions, or rate limits. The word 'Delete' implies mutation but lacks critical safety context.

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?

While brief at only four words, this represents under-specification rather than effective conciseness. The single sentence fails to earn its place because it adds no information beyond what is already in the tool name, offering no value to the agent.

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 graph operation with three parameters, no annotations, and no output schema, the description is grossly incomplete. It lacks explanation of the relation model (source-target-type triplet), deletion behavior, return values, or error conditions.

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?

With 0% schema description coverage, the description must compensate by explaining the parameter semantics. It completely omits what 'source', 'target', and 'type' represent (likely entity IDs and relation type), leaving all three parameters undocumented and ambiguous.

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?

Tautological: description restates name/title.

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_entity' or how it interacts with the graph structure. There are no prerequisites, warnings about orphaned entities, or references to the creation tool 'create_relations' mentioned.

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