Connect to MySQL Server

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description is not redundant. It adds critical lifecycle info: 'Not persisted to disk, but kept for the rest of the session under an alias', which explains the tool's side effects beyond safety. This is valuable transparency.

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 sentence that leads with the primary action and follows with essential caveats. It avoids fluff and is appropriately front-loaded, though slightly long. It earns its place with no wasted words.

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?

The description covers the tool's purpose, lifecycle, and alias persistence, which is sufficient for an agent to decide to call it. It does not describe what happens on failure or whether the connection becomes active immediately, but given no output schema and the simple nature of connection establishment, these gaps are minor.

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 100%, so all six parameters (host, port, user, alias, database, password) are fully documented in the schema. The description mentions 'explicit credentials' and 'alias' but does not add parameter-level detail beyond what the schema already provides. Baseline 3 applies.

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 'Connect' and the resource 'any MySQL server at runtime with explicit credentials'. It also explains the session-scoped alias behavior, which distinguishes it from siblings like use_connection. The purpose is unambiguous and actionable.

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 new connections and mentions alias for use_connection later, but does not explicitly say 'use use_connection for existing aliases' or provide exclusion criteria. While the context is clear, it leaves the agent to infer when not to use this tool.

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