Execute DDL

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the tool performs destructive operations (DROP, TRUNCATE) and requires readwrite mode, which is valuable safety-relevant information. It does not mention auto-commit or reversibility, but the destructive examples are a strong signal.

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 sentences, front-loaded with the core purpose and immediately followed by the essential prerequisite. No filler or redundant detail, every word earns its place.

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 single-parameter tool with no output schema and no annotations, the description covers the key elements: what the tool does, what the parameter should contain, and a required environment condition. It lacks details on return values or error behavior, but these are less critical for DDL execution.

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 documents 'sql' as 'DDL SQL statement' (100% coverage), so the baseline is 3. The description adds value by enumerating concrete DDL statement types, clarifying the expected content of the parameter beyond the schema's terse description.

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 'Execute DDL statements' with specific examples (CREATE, ALTER, DROP, TRUNCATE), making the tool's purpose unambiguous. It distinguishes from sibling tools like 'query' and 'execute' by explicitly scoping to DDL.

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 DDL statements and notes the ORACLE_MODE=readwrite prerequisite, but it does not explicitly state when to use this tool versus alternatives like 'query' or 'execute'. No exclusions or alternative recommendations are provided.

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