connect

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

With no annotations, the description only conveys the basic action and database types, lacking details on side effects like connection replacement behavior, authentication needs, or error scenarios.

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 a single efficient sentence, but it could be slightly expanded to include more parameter guidance without losing conciseness.

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 9 parameters and no output schema or annotations, the description omits critical details on parameter interactions, connection lifecycle, and how this tool integrates with siblings like execute_sql.

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 low (11%), yet the description only adds meaning for the 'type' parameter by listing the three database types, failing to explain other crucial parameters like connectionString, host, or ssl.

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 verb 'open or replace' and the resource 'dynamic PostgreSQL/MySQL/MongoDB connection', distinguishing it from sibling tools like close_connection or execute_sql.

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 implies usage for establishing or replacing connections but does not explicitly mention when not to use it or provide alternatives.

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