db_execute_write

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

With no annotations, the description carries the full burden. It discloses key behavior: only INSERT and UPDATE are executed, DELETE is rejected, and writes fail gracefully on read replicas. However, it doesn't explain what 'fails gracefully' entails (error vs no-op), nor mention commit behavior or side effects beyond the allowed operations.

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?

Single sentence, front-loaded with the core purpose, and includes the most important restriction (DELETE not allowed) and a notable operational behavior. The phrase 'fails gracefully' is slightly vague but efficient.

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 core operation and restrictions but omits anything about return values or post-conditions, which matters given there is no output schema. For a write tool with only two params, this is adequate but not complete – an agent might not know what to expect on success or failure.

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 100%, so both sql and timeout are documented in the schema. The description reiterates the INSERT/UPDATE restriction already present in the schema's sql property, adding no new parameter-specific semantics. Baseline of 3 applies.

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 write SQL queries limited to INSERT and UPDATE, explicitly forbidding DELETE. The resource (database) and verb are specific. It distinguishes from sibling db_execute_query by the 'write' qualifier, though it doesn't name the 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?

No explicit guidance is provided on when to choose this tool over db_execute_query or other siblings. The allowed operations imply usage for INSERT/UPDATE, and the DELETE prohibition tells agents what not to attempt, but there is no explicit when-to-use or alternative routing.

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