execute_unsafe_query

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

Beyond the destructiveHint annotation, the description adds crucial behavior: unrestricted SQL, CSV output for SELECT, row count for DML, and the auto_commit=false dry-run rollback mechanism. It also notes the writable connection requirement.

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?

Three sentences, front-loaded with the purpose, then output behavior, then dry-run and connection constraint. Every sentence adds value; no redundancy or fluff.

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 potentially destructive nature, the description covers execution scope, return types, dry-run safety mechanism, and a constraint. With a rich schema and output schema, this is fully adequate for an agent to select and invoke correctly.

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 baseline is 3. The description enriches meaning by explaining that auto_commit=false rolls back after reporting affected row count and clarifies SQL result types, adding value beyond schema parameter descriptions.

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 any SQL statement without restrictions' with specific output behavior (SELECT returns CSV; DML returns row count). This distinguishes it from sibling tools like execute_query and the dedicated insert/update/delete tools.

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 context is implied through 'without restrictions' and 'Only available on writable connections,' but no explicit when/when-not guidance or named alternatives is provided. The dry-run hint gives parameter usage guidance but not tool selection context.

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