Snowflake Resume Warehouse

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds nothing beyond that: it does not say whether resuming an already-running warehouse is a no-op, whether it requires ACCOUNTADMIN/OWNERSHIP privileges, or what the effect on billing and availability is.

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 no waste or filler. It is efficient, though its brevity borders on under-specification rather than genuine 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?

An output schema exists, so return-value explanation is not required, but for a state-mutating operation with a 0%-documented required parameter the description should at least state the suspended-state precondition and any privilege requirement. As written it is too thin for an operational tool.

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 0% and the single required parameter 'warehouse_name' is undocumented in the schema. The description never mentions the parameter at all, so it fails to compensate for the coverage gap (e.g., by noting the name format or whether it must exist).

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 gives a specific verb ('Resume') and resource ('a suspended virtual warehouse'), so the action is unambiguous. It does not name or distinguish itself from the obvious sibling snowflake_suspend_warehouse, but the name and verb make the pairing self-evident.

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 explicit guidance on when to use this tool, no stated precondition that the target warehouse must be in a suspended state, and no mention of the suspend counterpart. The agent must infer all usage context from the tool name alone.

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