Omni-MCP

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

With no annotations provided, the description carries full burden and does well by explaining key behaviors: it mounts a database, exposes the schema as MCP resources, and implies this is a setup step for querying. It doesn't mention potential errors (e.g., invalid paths), permissions, or persistence, but covers the core operational context adequately.

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?

Two sentences with zero waste: the first states the purpose and outcome, the second provides usage guidance. It is front-loaded with the main action and efficiently structured without 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 no annotations and no output schema, the description is complete enough for a simple setup tool: it explains what the tool does, how it integrates with the system (exposing schema), and the next step (using query_sqlite). It could mention error handling or limitations, but covers the essential context for 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 100%, so the schema already documents the single 'path' parameter fully. The description adds no additional parameter details beyond what the schema provides, such as file format requirements or examples, meeting the baseline for high schema coverage.

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 ('Mount'), the resource ('a local SQLite database file'), and the outcome ('Its schema is automatically exposed as an MCP resource'). It distinguishes from sibling 'mount_folder' and 'mount_url' by specifying SQLite databases, and from 'query_sqlite' by being a setup operation rather than a query tool.

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?

Explicitly states when to use this tool ('Mount a local SQLite database file') and when to use an alternative ('Use query_sqlite to run SELECT queries against it'). It differentiates from sibling tools by specifying the exact file type and provides clear guidance on the workflow.

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