Omni-MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates key behavioral traits: the read-only nature, SELECT-only restriction, JSON output format, and the 100-row limit. These are important constraints that help the agent understand the tool's behavior beyond basic functionality.

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 extremely concise and front-loaded with all essential information in a single sentence. Every word earns its place, communicating purpose, constraints, and output format without any wasted text. The structure is optimal for agent comprehension.

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?

For a query execution tool with no annotations and no output schema, the description provides good contextual completeness. It covers the read-only nature, query type restriction, output format, and row limit. The main gap is the lack of error handling information or result format details, but given the tool's relative simplicity, this is reasonably complete.

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?

The schema description coverage is 100%, with both parameters well-documented in the input schema. The description doesn't add any additional parameter semantics beyond what's already in the schema (path to database file, SQL SELECT query). This meets the baseline expectation when schema coverage is complete.

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 specific action ('Execute a read-only SQL query'), resource ('mounted SQLite database'), and scope ('SELECT only'). It distinguishes from siblings like mount_sqlite or list_mounts by focusing on query execution rather than database management operations.

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 clear context about when to use this tool: for read-only SELECT queries against mounted SQLite databases. However, it doesn't explicitly mention when NOT to use it (e.g., for write operations) or name specific alternatives among siblings, though the SELECT-only restriction implies alternatives would be needed for other operations.

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