SQLite Project Memory MCP

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

With no annotations provided, the description carries full burden. It discloses the core behavior (reuse or create with stable id), but misses critical details: what 'exact' matching entails (e.g., by name, type, or other fields), whether creation is idempotent, permission requirements, error handling, or rate limits. For a mutation tool with 7 parameters, this is insufficient.

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, efficient sentence that front-loads the core purpose. Every word earns its place: 'reuse' and 'create' define the dual behavior, 'exact entity' hints at matching logic, and 'generated stable id' clarifies the creation aspect. No wasted words or redundancy.

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 complexity (7 parameters, mutation operation, no annotations) and an output schema (which helps), the description is incomplete. It doesn't explain parameter roles, matching criteria, or behavioral nuances like idempotency. For a tool that both reads and writes, more context is needed to use it correctly without trial and error.

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 description must compensate. It mentions 'entity' and 'stable id' but doesn't explain any of the 7 parameters (e.g., what 'entity_type' or 'attributes' mean, how 'name' is used for matching). The description adds minimal value beyond the schema's property names, leaving parameters largely 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 clearly states the tool's purpose: 'Reuse an exact entity when it already exists or create one with a generated stable id.' It specifies the verb ('reuse' or 'create') and resource ('entity'), and distinguishes it from siblings like 'create_entity' (which only creates) and 'get_entity' (which only retrieves). However, it doesn't explicitly mention what constitutes an 'exact' match, leaving some ambiguity.

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 context: use this when you want to ensure an entity exists, reusing it if possible. It distinguishes from 'create_entity' by hinting at idempotent behavior. However, it lacks explicit guidance on when to choose this over alternatives like 'upsert_entity' or 'resolve_entity_by_name', and doesn't mention prerequisites or exclusions.

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