database_transaction

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

No annotations are provided, so the description carries the full burden. It only states 'execute' and 'multiple changes' without disclosing atomicity, rollback behavior, error handling, or permission requirements—critical for a transaction tool.

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?

One short sentence with no redundant wording, front-loading the verb and object. It is perfectly concise, though it sacrifices specificity.

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 complex mutating operation like a database transaction, the description is incomplete. It lacks information about atomicity, rollback, change structure, and expected outcomes, and the schema does not compensate with item definitions or an output schema.

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?

The schema already provides a description for the single parameter 'changes' ('Array of changes to apply'), giving 100% coverage. The description adds no extra semantics such as the structure of each change, item format, or examples.

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 action (execute) and resource (database transaction), which distinguishes it from sibling tools like database_rows_list by implying a write operation. However, 'multiple changes' is vague and doesn't specify what kinds of changes are supported.

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?

The name and description imply this tool is for transactional operations, but there is no explicit guidance on when to use it versus alternatives or when not to use it. No mention of batching vs. individual calls or prerequisites.

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