Warehouses Create Warehouse

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

Annotations already declare non-read-only, open-world, non-idempotent, and non-destructive behavior. The description adds almost no behavioral context beyond the resource type: it does not explain permission needs, default auto-suspend/resume implications, cost impact, or what happens when if_not_exists is true.

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 front-loaded sentence with no wasted words. However, for a tool with six parameters and low schema coverage, this brevity becomes under-specification rather than effective 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?

Although an output schema exists, the description does not cover key creation semantics: default warehouse size, idempotency via if_not_exists, or auto-suspend/auto-resume behavior. With six parameters and 17% schema coverage, the definition is incomplete for safe invocation.

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?

Schema description coverage is only 17%, and the description mentions none of the six parameters. It does not compensate for undocumented parameters such as auto_resume, auto_suspend, if_not_exists, warehouse_size, or comment.

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 specific verb and resource: 'Create a new virtual warehouse in Snowflake.' It clearly identifies the operation, though it does not distinguish this tool from siblings such as warehouses_drop_warehouse or warehouses_resize_warehouse.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites such as required privileges or the effect of if_not_exists. The implied action is creation, but the agent must infer context from the tool name and schema alone.

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