Run MySQL Query

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

Annotations set readOnlyHint=false, indicating writes are possible. The description adds the specific condition (MYSQL_ALLOW_WRITES=true) and lists the always-allowed query types, which is valuable behavioral context beyond the annotations. It does not mention result format or side effects, but the write permission gating is a key 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?

The description is two sentences, front-loaded with the main purpose and followed by a constraint. Every sentence contributes essential information without redundancy or fluff.

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 the tool's complexity (arbitrary SQL execution) and lack of output schema, the description covers the core purpose and critical permission constraints. Some details like return format or handling of non-listed DDL queries are omitted, but the description is sufficient for basic use.

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?

The input schema already describes both parameters (site and query) with 100% coverage, including an example for query. The description does not add meaning beyond the schema; it only repeats that it executes a SQL query, so the baseline of 3 is appropriate.

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 'Execute a SQL query against the WordPress database', using the specific verb 'Execute' and identifying the resource. It also enumerates allowed query types (SELECT, SHOW, DESCRIBE, EXPLAIN) and write conditions, which distinguishes this tool from siblings like wp_cli_run (WP-CLI commands) and mysql_schema (schema browsing).

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 clear context on when the tool can be used: read-only queries are always allowed, while write operations (INSERT, UPDATE, DELETE) are gated behind MYSQL_ALLOW_WRITES=true. It does not explicitly name alternative tools or exclusions, but it gives sufficient guidance for safe usage.

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