execute_dml

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

Describes transaction behavior, commit, rollback on error, return format, and no trailing semicolon. No annotations provided, so description carries the burden; adequate.

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 sentences, front-loaded with main purpose. No redundant 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?

Covers return value, error handling, parameter hints, and sibling reference. Lacks prerequisites like connection required, but sufficient for a simple tool.

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 0%. Description provides minimal guidance: 'database: key from list_databases' and 'sql: one DML statement'. Adds value but lacks constraints or examples.

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?

Description clearly states it executes a single DML statement (INSERT, UPDATE, DELETE) with commit. It distinguishes from siblings by mentioning execute_script for multiple statements.

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 says 'Use execute_script to run multiple statements.' Implicitly distinguishes from execute_ddl and run_query, but could be more explicit.

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