CockroachDB MCP Server

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

With no annotations provided, the description carries full burden but provides minimal behavioral context. It mentions creating a connection pool (important behavior) but doesn't disclose whether this is persistent, how connections are managed, authentication requirements beyond parameters, rate limits, error handling, or what happens to existing connections. For a critical infrastructure tool with 9 required parameters, this is insufficient disclosure.

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?

Well-structured with purpose statement followed by organized parameter documentation. The Args/Returns format is clear. Some redundancy exists (e.g., 'CockroachDB' repeated in parameter descriptions), but overall efficient for documenting 9 parameters. Every sentence serves a purpose.

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 complex connection tool with 9 required parameters and no annotations/output schema, the description covers parameters well but lacks critical context about connection behavior, persistence, error cases, and relationship to other tools. The Returns section is vague ('success message or error message'). Given the tool's importance and complexity, more behavioral context would be needed for full completeness.

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, the description fully compensates by documenting all 9 parameters with clear names, types, defaults, and important details like possible values for sslmode. The Args section provides complete parameter semantics that the schema lacks, including default values and value constraints that aren't in the schema's enum field.

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 action ('Connect to a CockroachDB database and create a connection pool') with specific technology context. It distinguishes from siblings like 'connect' (which appears to be a different tool) and 'switch_database' by focusing on initial connection establishment rather than switching or other operations. However, it doesn't explicitly contrast with all similar-sounding siblings.

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 'connect' or 'switch_database'. It doesn't mention prerequisites, when this connection is needed versus other database operations, or any context about connection lifecycle management. 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.