exec_ddl_sql

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

No annotations are provided, so the description carries the full burden of behavioral disclosure for a high-risk mutation tool. It does not say that DDL is typically irreversible, whether the statement auto-commits, whether it can drop data, what privileges are required, or what the response looks like. For a destructive operation this is a substantial gap.

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 short sentences plus an args block, with the core action front-loaded and no filler. The Args section is slightly redundant given the one-parameter schema, but nothing is padded.

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?

No annotations, no output schema, and a high-consequence DDL operation leaves the agent without risk, commit, or permission context. The parameter name mismatch against the schema compounds the incompleteness.

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 description coverage is 0% for the single required parameter, and the description actively adds confusion: it documents the argument as 'query', while the schema requires a property named 'execsql'. It conveys only that the value is SQL to execute, with no dialect, length, or multi-statement guidance.

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 states a specific verb (execute) and resource class (create/drop/alter DDL against an Oracle database), which cleanly separates it from the sibling exec_dml_sql and exec_pro_sql. It does not name those siblings explicitly, so the differentiation is inferable from the tool name rather than spelled out in the text.

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?

Usage is implied by enumerating create/drop/alter, which tells an agent this is the DDL path as opposed to DML or stored procedures. There is no explicit when-to-use statement, no when-not-to-use, and no mention of prerequisites such as target schema or permissions.

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