MySQL MCP Server

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

No annotations are provided, so the description carries the full burden. While it mentions 'data modification' implying mutation, it lacks critical behavioral details such as permissions required, whether changes are reversible, transaction handling, error behavior, or rate limits. This is a significant gap for a potentially destructive tool.

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 extremely concise and front-loaded: a single sentence that efficiently communicates purpose, scope, and exclusion. Every word earns its place with zero wasted text.

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 this is a potentially destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address critical context like what happens on execution (e.g., confirmation, rollback), error handling, or return values, leaving significant gaps for safe agent operation.

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 the schema already documents the single 'sql' parameter. The description adds minimal value beyond the schema by reinforcing that SELECT statements are not allowed, but doesn't provide additional syntax, format, or validation details. Baseline 3 is appropriate when schema does the heavy lifting.

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 tool's purpose with a specific verb ('execute') and resource ('data modification SQL statement'), listing specific SQL operations (INSERT, UPDATE, DELETE, etc.). It distinguishes from the sibling 'query' tool by explicitly excluding SELECT statements.

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 explicit guidance on when to use this tool vs alternatives: it specifies 'data modification SQL statement' and explicitly states 'SELECT statements are not allowed here; use the "query" tool instead,' naming the alternative tool directly.

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