execute_query

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly states the read-only default and the required MYSQL_ALLOW_WRITE=true and WHERE clause for write operations, which is valuable context beyond the schema. However, it does not mention pagination, limits, or error behavior.

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 primary purpose and followed by an important caveat. No wasted words; every sentence delivers actionable information.

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 tool has an output schema, so return values are likely covered, but the description omits the database parameter's purpose and does not reference sibling alternatives. The read-only and write-restriction details are helpful, but the missing param semantics leave a notable gap.

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 indirectly explains the query parameter as a SQL query but does not describe the database parameter at all. The description adds minimal meaning beyond the schema's bare property definitions.

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 executes SQL queries, specifically read-only ones like SELECT, SHOW, and DESCRIBE. This distinguishes it from sibling tools that handle specific tasks like listing databases or tables.

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 arbitrary read-only SQL queries and mentions write operations under specific conditions, but it does not explicitly compare with sibling tools or state when to prefer this tool over list_databases, list_tables, or describe_table. Context is present, but exclusions are not.

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