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. It mentions that archiving preserves 'history or related project memory,' which adds some context about data retention. However, it does not cover critical aspects such as required permissions, whether the action is reversible, rate limits, or what the archived status entails, leaving significant gaps for a mutation tool.

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, well-structured sentence that efficiently conveys the core action and key distinction from deletion. It is front-loaded with the main purpose and avoids unnecessary details, making it highly concise and effective for quick understanding.

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 that there is an output schema (which handles return values), no annotations, and low schema coverage, the description is moderately complete. It clarifies the tool's purpose and data retention aspect, but as a mutation tool with three parameters, it lacks details on behavioral traits and parameter meanings, making it somewhat incomplete for safe and effective use by an AI agent.

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%, so the schema provides no parameter details. The description does not mention any parameters explicitly, such as 'entity_id,' 'reason,' or 'archived_status,' nor does it explain their meanings or usage. With three parameters (one required) and no compensation in the description, the baseline score of 3 reflects minimal adequacy, as the description fails to add semantic value beyond the schema's structure.

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 action ('Archive') and the resource ('an entity'), and distinguishes it from deletion by specifying 'without deleting its history or related project memory.' This differentiates it from sibling tools like 'delete_entity' and 'update_entity,' making the purpose specific and unambiguous.

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 implies usage by contrasting with deletion ('without deleting its history or related project memory'), suggesting it's for preserving data while marking it as archived. However, it lacks explicit guidance on when to use this tool versus alternatives like 'delete_entity' or 'update_entity,' and does not mention prerequisites or exclusions, leaving some context to inference.

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