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. It discloses that queries are 'constrained' and 'read-only', which is useful behavioral context. However, it doesn't cover critical aspects like permissions needed, rate limits, error handling, or what 'constrained' entails (e.g., query complexity limits). This leaves significant gaps for a tool that executes SQL queries.

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 with no wasted words. It front-loads key information ('run a constrained read-only SQL query') and uses clear, structured phrasing. Every part earns its place by specifying scope and use cases.

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 a SQL query tool with 3 parameters, 0% schema coverage, no annotations, but an output schema exists, the description is partially complete. It covers the core purpose and constraints but misses parameter details and behavioral traits. The output schema reduces the need to explain return values, but more context on usage and limitations is warranted.

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 for undocumented parameters. It mentions 'SQL query' which hints at the 'sql' parameter, but doesn't explain 'parameters' (for query placeholders) or 'limit' (for result pagination). The description adds minimal meaning beyond the schema, failing to address the coverage gap adequately.

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 with specific verbs ('run', 'constrained', 'read-only') and resource ('SQL query'), and distinguishes it from siblings by specifying it's for 'diagnostics, analytics, and ad hoc retrieval'. However, it doesn't explicitly differentiate from similar tools like 'query_view' or 'search_content', which might also involve querying.

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 provides some context by mentioning use cases ('diagnostics, analytics, and ad hoc retrieval'), but it lacks explicit guidance on when to use this tool versus alternatives like 'query_view' or 'search_content'. No exclusions or prerequisites are stated, leaving the agent to infer usage.

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