set_warehouse

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

There are no annotations, so the description carries the behavioral disclosure burden. It does mention that the warehouse is 'current' and 'for the session,' indicating a stateful change, and it states the return is a confirmation string. However, it omits session lifetime, overwrite behavior, prerequisites such as the warehouse needing to exist, and permission requirements.

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 core purpose is front-loaded in one clear sentence, followed by compact Args/Returns sections. The ctx line is unnecessary and potentially confusing, but overall the description is appropriately short and structured.

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 simple one-parameter setter with no output schema, the description covers the purpose, parameter meaning, and return value. It is adequate for basic invocation, but it lacks usage guidance relative to sibling tools and includes an inconsistent ctx parameter, leaving some gaps.

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 adds meaning by saying 'warehouse' accepts a Name or ID, which is more informative than the schema's plain string type. However, it also lists a 'ctx' argument that is not present in the input schema, which could mislead an agent into passing an unsupported parameter.

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 states a clear verb-object-resource: 'Set the current warehouse for the session,' which identifies the operation and scope. It is distinguishable from create/list warehouse tools by the action and from other set_* tools by the resource name, though it does not explicitly contrast with them.

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 is given on when to use this tool versus set_workspace, set_lakehouse, set_table, or list_warehouses. The session-setting context is implied but no exclusions or alternative tool suggestions are provided.

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