CockroachDB 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 adds valuable context about confirmations for security and typical use cases, but does not cover critical aspects like required permissions, whether the action is reversible, potential side effects on dependent objects, or error conditions beyond generic error messages.

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 and front-loaded with the core purpose in the first sentence. The Args and Returns sections are structured but slightly verbose; every sentence earns its place, though the 'always with the necessary confirmations' phrase could be more concise.

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 high complexity of a destructive database operation with no annotations and no output schema, the description is incomplete. It covers the basic purpose and parameter but lacks details on permissions, safety mechanisms, return format specifics, and error handling, which are critical for such a tool.

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 0%, so the description must compensate. It explicitly documents the single parameter (table_name) with its type and purpose, adding meaning beyond the bare schema. However, it does not provide format constraints, examples, or validation rules for the table name.

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 ('deletion of existing tables') and resource ('tables from the database'), distinguishing it from siblings like drop_database, drop_index, and drop_view. It goes beyond the tool name by specifying the scope (existing tables) and context (database).

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 for when to use this tool ('cleaning up test environments or managing schema changes'), but does not explicitly state when not to use it or name alternatives. It implies usage scenarios but lacks explicit exclusions or comparisons to sibling tools like drop_database.

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