MCP Memory SQLite

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

With no annotations provided, the description carries full disclosure burden but offers minimal behavioral context. It does not specify the return format, pagination limits, what 'recent' quantifies, or whether this is a safe read-only operation despite the 'Get' verb implying so.

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 the single-sentence structure avoids verbosity, the extreme brevity constitutes under-specification rather than efficient communication. The sentence fails to earn its place by adding value beyond the tool name.

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 graph query tool with no output schema, the description inadequately explains return values. It mentions 'entities and their relations' but omits structure, depth of relation traversal, result count limits, and the definition of 'recent'—critical gaps for a retrieval tool.

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?

Input schema contains zero parameters. Per scoring guidelines, zero-parameter tools receive a baseline score of 4 since there are no parameter semantics to describe beyond the schema itself.

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?

No guidance provided on when to use this versus alternatives. Given siblings include specific entity retrieval (get_entity_with_relations) and search (search_nodes), the description should clarify that this returns unfiltered recent activity rather than targeted queries.

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