⚠️ TRANSACTION: Begin transaction for atomic operations. Groups queries into single unit. Holds locks until commit/rollback.

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

The description mentions 'holds locks until commit/rollback', which adds behavioral context beyond a simple 'begin transaction'. However, with no annotations, more details (e.g., timeout, nesting, impact on other connections) would be beneficial. The description does not contradict any annotations as none are provided.

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 very concise, but it repeats the title verbatim. It front-loads the purpose but does not add new information beyond the title. It could be more structured and earn its length.

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 is inadequate given the tool's complexity (transaction management, 26 sibling tools). It does not explain prerequisites (e.g., database must be open), default behavior if no database_name specified, or that transaction must be active for subsequent operations. No output schema or annotations to compensate.

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 only parameter 'database_name' is optional with no description. Schema description coverage is 0%, so the description provides no information about its purpose or default behavior.

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 on when to use this tool versus executing queries without a transaction or versus other database tools. The description lacks context on prerequisites or typical usage patterns.

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