⚠️ 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 discloses that it holds locks and groups queries, which is relevant behavioral information. However, without annotations, it omits details like potential blocking, permission requirements, or cleanup obligations.

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 sentence that communicates the core function efficiently. It uses a warning symbol for emphasis, but the conciseness sacrifices some detail.

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 transactional tool, the description lacks information on transaction life cycle (commit/rollback required), concurrency implications, and parameter usage. The absence of output schema highlights the need for more context.

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 and has no documentation in the description. With 0% schema description coverage, the description must explain parameters but fails to do so, leaving the agent without guidance.

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?

The description implies usage for atomic operations but lacks explicit guidance on when to use or avoid this tool. It does not mention prerequisites (e.g., an open database) or scenarios where transactions should not be used.

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