SQLite Project Memory MCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The phrase 'Add a piece of content' implies a write/mutation operation, but the description fails to disclose critical behavioral traits such as whether this requires specific permissions, if it's idempotent, what happens on conflicts, or how it interacts with existing content. For a mutation tool with zero annotation coverage, this is a significant gap.

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 extremely concise at just 7 words in a single sentence. While this brevity comes at the cost of completeness, every word directly contributes to stating the core action without any fluff or redundant phrasing. It's front-loaded with the essential verb and object.

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 a mutation tool with 4 parameters, 0% schema description coverage, no annotations, and multiple similar sibling tools, the description is completely inadequate. While an output schema exists (which reduces the need to describe return values), the description fails to provide necessary context about the tool's purpose, usage, behavior, or parameters. This leaves the agent poorly equipped to use the tool correctly.

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%, meaning none of the 4 parameters have descriptions in the schema. The tool description provides no information about parameter meanings, expected formats, or usage examples. It doesn't explain what 'entity_id', 'content_type', 'body', or 'content_id' represent, leaving all parameters completely undocumented.

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 'Add a piece of content to an entity' is a tautology that essentially restates the tool name 'append_content' with minimal elaboration. It specifies the verb 'add' and resource 'content to an entity', but lacks specificity about what 'content' means or how it differs from sibling tools like 'write_content' or 'update_entity'. This provides only basic direction without clear 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?

No guidance is provided on when to use this tool versus alternatives. With sibling tools like 'write_content', 'update_entity', and 'create_entity' available, the description offers no context about appropriate use cases, prerequisites, or exclusions. This leaves the agent without necessary decision-making information.

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