mysql_execute_query

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states that it executes SQL but does not disclose potential side effects (e.g., data modification, DDL execution), required permissions, or transaction behavior. This is a significant gap for a tool that can run arbitrary SQL.

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 with no redundant wording. It is appropriately short for the tool's apparent simplicity, though it lacks substance that could be added without being wordy.

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 executes arbitrary SQL, it has high complexity and potential risk. The description provides no information about return format, how the limit parameter affects results, or connection alias behavior beyond the schema. The combination of no annotations and a minimal description makes it incomplete for an agent to invoke safely.

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%, with each parameter (query, alias, limit) having a clear description. The tool description itself adds no additional meaning, but since the schema already documents the parameters, a baseline score 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 'Execute SQL query on MySQL database' clearly specifies the action (execute) and resource (SQL query on MySQL). It is distinct from sibling tools like mysql_show_tables or mysql_describe_table, though it does not explicitly differentiate from mysql_execute_batch beyond the name.

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 no guidance on when to use this tool versus alternatives. It does not mention that read-only operations could be done with dedicated tools like mysql_show_tables, nor does it suggest when to use mysql_execute_batch instead.

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