execute

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

The description discloses a key behavior—returning the number of affected rows—and labels the operation as a write. However, there are no annotations, and it omits additional important details such as transaction handling, permission requirements, or the risks of DROP statements.

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 short, front-loaded with the core purpose, and includes concise examples. Every sentence adds value without redundancy.

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?

For a one-parameter tool with an output schema, the description is adequate but not fully complete. It would benefit from explicit warnings about destructive statements (DROP) and a note to use query for read-only SELECT, given the tool's powerful nature.

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 schema is bare (0% coverage) with only 'sql' as a string parameter. The description compensates with concrete examples showing how to pass entire SQL statements, adding meaning beyond the schema's mere type definition.

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 write SQL statements (CREATE, INSERT, UPDATE, DELETE, ALTER, DROP), identifying a specific action and resource. This distinguishes it from sibling tools like query (for reads) and list_tables (for metadata).

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 by enumerating the statement types it handles, implying it is for write operations. It does not explicitly name alternatives like query for SELECT, but the sibling list and the 'write SQL' phrase give sufficient guidance for typical usage.

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