Execute DML

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

With no annotations provided, the description carries the full burden. It discloses critical behavior: the readwrite mode requirement and auto-commit on success. This goes beyond a simple execution statement, though it does not describe error handling or return format.

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 a single, compact sentence set with three clear clauses: purpose, prerequisite, and behavior. Every word contributes meaning, and it is front-loaded with the action.

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?

The description covers the essential aspects for a DML execution tool: what it executes, the mode requirement, and commit behavior. It does not mention output or error handling, but since there is no output schema, such details are less necessary. Overall, it is adequately complete for its complexity.

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% for both parameters, and the description adds no additional semantics beyond what the schema already provides. The schema already explicates the sql and binds fields, so the description provides no extra value here.

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 identifies the tool's function: executing DML statements (INSERT, UPDATE, DELETE, MERGE). It uses a specific verb plus resource and distinguishes from sibling tools like query (SELECT) and ddl (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 provides a clear prerequisite (ORACLE_MODE=readwrite) and the statement types covered, implying it is for DML as opposed to other siblings. However, it does not explicitly name alternatives for SELECT or DDL, so it lacks explicit exclusions.

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