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 full burden. It mentions the tool writes files (implied mutation) and requires user requests, but lacks details on permissions, file system impact, error handling, or output behavior. The description adds minimal behavioral context beyond the basic action.

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 usage condition. It's front-loaded with the main purpose and has zero wasted words, making it easy to parse.

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 6 parameters with 0% schema coverage, no annotations, and sibling tools like 'render_markdown_views', the description is incomplete. It doesn't explain what 'markdown views' are, how parameters interact, or what the output schema returns. The presence of an output schema reduces the need to describe returns, but other gaps remain significant.

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 6 undocumented parameters. It doesn't explain any parameters like 'view_names', 'output_dir', or 'user_requested', leaving their purposes unclear. The description adds no parameter semantics beyond the basic action.

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 states the tool 'Write[s] generated markdown views' which provides a verb ('write') and resource ('markdown views'), but it's vague about what 'markdown views' are and doesn't distinguish from siblings like 'render_markdown_views' or 'write_content'. The phrase 'human-readable artifact' adds some context but remains general.

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 explicitly states 'only after an explicit user request for a human-readable artifact,' providing clear when-to-use guidance. This distinguishes it from tools that might generate views automatically or for other purposes, though it doesn't name specific alternatives.

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