Snowflake Describe Warehouse

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only that the result includes running state; with annotations carrying the load, that minimal extra context warrants a 3 rather than less.

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 filler, which is appropriately terse for a one-parameter read tool. It is arguably too terse to carry any guidance, but there is no wasted language.

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 values need not be enumerated, and annotations cover the safety profile. For a simple one-parameter describe tool the description is nearly sufficient, with only the parameter format and not-found behavior left unstated.

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?

One required parameter with 0% schema description coverage, so the description must compensate and only partially does: 'a specific virtual warehouse' implies warehouse_name identifies the target, but nothing is said about accepted format (name vs. identifier vs. quoted name) or behavior when the warehouse does not 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?

States a specific verb (describe) and resource (a specific virtual warehouse) plus the scope of the output (details and running state). It clearly distinguishes inspection from the mutating siblings (create/drop/resume/suspend/resize), though it never names an alternative explicitly.

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?

Usage is only implied: the phrasing 'a specific virtual warehouse' suggests inspecting an existing warehouse by name rather than listing them, but there is no explicit when-to-use, no exclusion pointing to snowflake_list_warehouses or snowflake_get_warehouse_load_history, and no stated prerequisites.

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