⚠️ DESTRUCTIVE: Execute INSERT/UPDATE/DELETE with params.

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

No annotations are provided, so the description's DESTRUCTIVE warning carries the burden of conveying that this is a mutating operation. It adds a meaningful safety signal but does not disclose transaction behavior, rollback options, or side effects beyond the label.

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 a single front-loaded sentence with no filler, but it is a direct duplicate of the title. While compact, it under-specifies the tool, relying entirely on the warning for substance.

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?

For a destructive write tool with no annotations, an output schema, or parameter descriptions, the context provided is far too sparse. It omits safety practices, database_name usage, transaction interplay, and expected outcomes.

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 the description only says 'with params,' offering no meaning for the query, params, or database_name fields. It fails to compensate for the schema's lack of 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?

Tautological: description restates name/title.

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 guidance is given on when to use this tool versus alternatives such as execute_read_query, execute_schema_query, or transaction-related tools. There are no exclusions or context about transactional boundaries or prerequisites.

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