execute_dml

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions the destructive nature (INSERT, UPDATE, DELETE) and the connection mode requirement, but fails to describe transaction behavior (e.g., default auto-commit via the commit parameter, which is only in schema), error handling, or return value. This is insufficient for a mutation tool.

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 extremely concise, consisting of two sentences that front-load the core purpose and then add a critical constraint. Every word is necessary and contributes to clarity.

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 the lack of an output schema, the description could explain what the tool returns (e.g., number of rows affected). It does not cover transaction details beyond the commit parameter hint, ignoring error scenarios or connection validation. It is adequate but not thorough.

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%, so the baseline is 3. The description does not add any information beyond the schema descriptions for the three parameters (sql, commit, connection). It only provides general context about DML operations, which does not enhance parameter understanding.

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 the tool executes DML statements (INSERT, UPDATE, DELETE) on an Oracle database, with a specific requirement for readwrite mode. This verb+resource combination is precise and distinguishes it from sibling tools like execute_query (for SELECT) and execute_plsql (for PL/SQL).

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 data modification by listing INSERT, UPDATE, DELETE, and notes the readwrite mode requirement. However, it does not explicitly state when not to use this tool (e.g., for SELECT queries) or name alternative tools like execute_query. The guidance is clear but not explicit.

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