Vertica MCP Server

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 mentions safety features like size detection, pagination, and timeout support, which adds some context. However, it doesn't detail critical behaviors such as what happens when thresholds are exceeded, how pagination works in practice, or error handling for timeouts, leaving significant gaps for a tool with 8 parameters.

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 appropriately sized with a clear summary sentence followed by a structured parameter list. Each parameter explanation is brief and focused, though the initial summary could be more front-loaded with key usage context. There's minimal wasted text, making it efficient for an agent 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 the tool's complexity (8 parameters, no annotations, no output schema), the description is moderately complete. It covers parameter semantics well but lacks behavioral details like response format, error conditions, and sibling differentiation. For a safe query execution tool with many options, more context on outcomes and trade-offs would be beneficial.

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 provides a helpful list of all 8 parameters with brief explanations that add meaning beyond the schema's titles and types. For example, it clarifies 'row_threshold' as 'Maximum rows before requiring confirmation' and 'precount' as 'Count total rows for large results (expensive)', which significantly enhances understanding.

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 executes SQL queries with safety features like size detection, pagination, and timeout support. It specifies the verb ('execute') and resource ('SQL query') but doesn't explicitly differentiate from siblings like 'execute_query_paginated' or 'execute_query_stream' beyond the 'safely' aspect in the name.

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 no guidance on when to use this tool versus alternatives like 'execute_query_paginated' or 'execute_query_stream'. It mentions features like pagination and streaming modes but doesn't specify scenarios where this tool is preferred over its siblings, leaving the agent to infer usage from parameter names alone.

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