Queries Execute Dml

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds only 'Requires confirmation', but never explains what confirmation means operationally (e.g. that confirm must be set true, or whether a dry-run occurs).

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?

A single tight sentence with no filler; the destructive scope and the confirmation requirement are both front-loaded.

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?

An output schema exists, so return values need no prose. However, for a destructive, non-idempotent DML tool with 0% parameter documentation, the description leaves the confirm workflow and statement constraints unaddressed, which is a meaningful gap.

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% and neither parameter is documented in the schema. The description alludes to the 'statement' parameter conceptually but never clarifies its format, and the 'confirm' boolean — critical for this destructive tool — is entirely unexplained.

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?

States a specific verb (Execute) and resource (data modification SQL statement) and enumerates the statement classes (INSERT, UPDATE, DELETE, MERGE, CREATE). This clearly separates it from the read-oriented sibling queries_query, though it never names that sibling explicitly.

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?

'Requires confirmation' hints at a prerequisite, but the description gives no explicit when-to-use vs when-not, and does not route the agent to queries_query for SELECT-type reads or to the transaction tools (begin/commit/rollback). Usage is only implied.

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