db_connect

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

With no annotations, the description carries full responsibility for disclosing behavior. It says the tool connects a session and lists supported engines, but it does not mention side effects, connection persistence, authentication requirements, or implications of the allow_write parameter. An agent is left without a clear picture of what 'connect' changes in the system.

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, front-loaded sentence with no filler. It is concise and communicates the core action and engine options immediately, though the brevity leaves out important context that is penalized in other dimensions.

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 tool with four parameters, no annotations, and an output schema not shown, the description is too sparse. It fails to explain format expectations for 'url', the meaning of 'allow_write', or what happens upon successful connection. An agent cannot confidently invoke this tool correctly based solely on the description.

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 description must compensate. It does add meaning for 'engine' by enumerating supported values and hints at 'session_name' with 'named session', but it says nothing about the critical 'url' parameter or the 'allow_write' flag. The compensation is partial at best.

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') and the resource ('a named session'), and the engine list adds specificity about supported database types. However, it does not explicitly differentiate itself from siblings like db_status or db_disconnect, relying on the 'connect' verb to imply its role.

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?

There is no guidance on when to use this tool versus alternatives such as db_status or db_query, nor any mention of prerequisites like requiring a server to be reachable. The description only states what the tool does, not when or when not to invoke it.

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