MCP Vertica

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'progress reporting and logging' via the ctx parameter, which adds some context, but fails to disclose critical traits: whether this is a read/write operation (implied write from 'copy'), potential side effects (e.g., table locking, data overwriting), error handling, or performance considerations. For a data mutation tool with zero annotation coverage, this is inadequate.

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 well-structured and concise: a clear purpose statement followed by Args and Returns sections. Every sentence adds value, with no redundant information. It could be slightly more front-loaded by emphasizing the core action earlier, but overall it's efficient.

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 complexity (a data mutation tool with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain return values beyond 'status message' (no format or examples), error conditions, or behavioral nuances like transaction handling. For a tool that modifies database state, this leaves significant gaps for an 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 0%, so the schema provides no parameter descriptions. The description compensates by listing parameters (ctx, schema, table, data) with brief explanations, adding meaning beyond the bare schema. However, it doesn't detail formats (e.g., data structure, schema/table naming rules) or constraints, leaving gaps. With 3 parameters and partial coverage, a baseline 3 is appropriate.

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: 'Copy data into a Vertica table using COPY command.' It specifies the verb ('copy'), resource ('data'), and target ('Vertica table'), though it doesn't explicitly differentiate from sibling tools like execute_query (which might also insert data). The mention of 'COPY command' adds technical specificity.

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. It doesn't mention sibling tools like execute_query (which could potentially insert data via SQL), nor does it specify prerequisites or contexts for usage. The agent must infer usage from the purpose alone.

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