execute_script

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

Describes key behavioral traits: each statement runs in its own transaction, no global rollback on failure, returns per-statement status. This fully informs the agent of side effects despite no annotations.

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?

Four concise sentences front-loading critical information (purpose, transaction behavior, rollback, return format, alternative usage). No unnecessary words.

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 no output schema, the description explains return format (per-statement status lines) and covers all critical aspects for using the tool: database selection, script format, transaction isolation, and error handling.

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 coverage is 100%, and the description repeats the schema's parameter descriptions without adding new meaning. The warning is already in the schema, so no additional value beyond baseline.

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 it executes multiple SQL statements separated by semicolons, each in its own transaction, with no global rollback. It also distinguishes from sibling tools execute_ddl and execute_dml.

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?

Explicitly advises preferring execute_ddl or execute_dml for single statements, implying this tool is for multiple statements. The warning about no rollback guides appropriate use cases.

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