MCP Memory SQLite

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 but offers minimal details. It mentions retrieving 'all' relations but does not specify traversal depth (immediate neighbors only? transitive closure?), response format, or error behavior when the named entity does not exist.

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 sentence that efficiently restates the title. While not verbose, it is underspecified for the complexity of graph traversal operations—every sentence earns its place, but critical information is missing that should have been included.

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 complexity of knowledge graph traversal, zero schema descriptions, no annotations, and no output schema, the description is inadequate. It does not hint at the return structure (e.g., nested entity objects vs. edge lists), pagination behavior, or relation depth limits.

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% for the single 'name' parameter, and the description completely fails to compensate. It does not indicate whether 'name' refers to a unique identifier, display label, or URI format, leaving the agent without guidance on how to construct valid inputs.

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?

Provides no guidance on when to use this tool versus alternatives like 'search_nodes' (for finding entities) or 'read_graph' (for bulk access). Does not mention prerequisites such as needing to know the entity name in advance, nor does it warn about performance implications of fetching 'all' relations.

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