execute_ddl

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

Discloses that changes are committed immediately, a key behavioral trait. No annotations exist, but the description lacks details on permissions, rollback, or result 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?

Two concise sentences, front-loaded with the core action and a critical warning. 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?

Adequate for a simple tool with one parameter and no output schema. Missing information about return value (e.g., affected rows or success indicator) would be helpful.

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%. The tool description does not add extra meaning beyond the schema's parameter description, which includes the 'without trailing semicolon' instruction.

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?

Clearly states the tool executes DDL/DML statements and lists examples. However, it does not differentiate from sibling 'execute_query' which may also handle 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?

Includes a caution about immediate commitment, implying use with care. No explicit guidance on when not to use or references to alternatives like execute_query for SELECT.

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