Vertica MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'pagination support and result size limits' which gives some context about output behavior, but doesn't address critical aspects like whether this is a read-only operation, what permissions are required, error handling, rate limits, or what the actual return format looks like.

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 - a single sentence that efficiently communicates the core functionality. It's front-loaded with the main purpose and wastes no words on unnecessary elaboration.

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 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the query language, result format, error conditions, or how pagination actually works in practice. The mention of 'pagination support' is too vague for proper agent understanding.

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?

With 0% schema description coverage and 5 parameters (only 1 required), the description provides no information about any parameters. It doesn't explain what 'query' should contain, what 'limit' and 'offset' control, what 'include_columns' affects, or how 'timeout' works. The description fails to compensate for the complete lack of schema documentation.

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 as 'Execute query with pagination support and result size limits' - a specific verb ('execute') and resource ('query') with key capabilities. However, it doesn't distinguish this from sibling tools like 'execute_query_stream' or 'run_query_safely', which likely have different execution characteristics.

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. With siblings like 'execute_query_stream', 'run_query_safely', and 'profile_query' available, there's no indication of when paginated execution is preferred over streaming, safe execution, or profiling approaches.

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