snowflake_use_connection

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

The description transparently indicates that the tool switches the active Snowflake session, which is a state-changing behavior. It does not mention any data modifications or side effects, and with no annotations, it carries the full burden; however, the stated behavior is clear and no contradictions exist.

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, focused sentence that front-loads the verb and resource. It contains no redundant or vague terms.

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 tool is simple with one parameter, and the description explains both the action and the parameter's origin. Since an output schema is present, not describing return values is acceptable; the description is complete for invoking the tool correctly.

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 description clarifies that connection_name refers to a named profile in ~/.snowflake/connections.toml, adding meaning beyond the schema's bare string type. This is the only parameter, and the description adequately defines its semantics.

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 (switch) and the resource (active Snowflake session to a different connection profile), and specifies the source file (~/.snowflake/connections.toml). This distinguishes it from the many query and admin sibling tools.

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 the use case—changing the active connection context—but does not explicitly say when to use it (e.g., before running queries on a different warehouse) or compare it to alternatives. It provides the mechanism but lacks explicit usage timing.

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