snowflake_begin_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 the bare action; it does not disclose that the session state changes, that subsequent operations become part of this transaction, or that a commit or rollback is required. For a transaction operation, this is a significant transparency gap.

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?

A single, front-loaded sentence with zero wasted words. It is appropriately concise for a parameterless tool, though more context could have been added without harming conciseness.

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?

Despite having an output schema and no parameters, the description is too thin for a transaction control operation. It omits essential context like the need to pair with commit or rollback, the session-scoped nature, and the effect on subsequent queries. An agent cannot fully infer correct usage from this definition alone.

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?

There are zero parameters, and the schema documents none, so the baseline of 4 is appropriate. The description adds nothing about parameters, which is fine since none exist. No compensation is needed.

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 ('begin') and target (explicit transaction on active session), and is distinct from sibling tools like commit_transaction. It leaves no ambiguity about what operation is performed.

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 alternatives or what precedes/follows it. It does not mention that it should be used before executing multiple statements or that it requires a subsequent commit/rollback, nor does it point to any sibling tools for comparison.

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