snowflake_list_warehouses

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only list operation and scopes to 'in the account', but does not explicitly state read-only nature, mention pagination or filtering behavior, or note any permission requirements. It is not misleading, but it adds little beyond the purpose.

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 efficient sentence that front-loads the core action and resource. There is no redundant phrasing or unnecessary detail; it wastes no words.

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?

Given that an output schema exists, return fields are covered externally. However, the description fails to document the 'pattern' parameter and offers no usage guidance relative to sibling tools. For a tool with one optional parameter and a clear list purpose, this is adequate but leaves the parameter semantics and selection context incomplete.

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 sole parameter 'pattern' is not described in the schema (only its type and default are given), and the description does not mention it at all. With 0% schema coverage, the description should compensate by explaining what the parameter filters (e.g., a name pattern), but it does not. The agent is left to guess its meaning.

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 ('List') and a specific resource ('virtual warehouses in the account'), and it names distinguishing attributes (size, state, auto-suspend configurations). This separates it from other listing tools like snowflake_list_tables or snowflake_list_schemas, and from single-warehouse tools like snowflake_describe_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?

No explicit when-to-use or when-not-to-use guidance is given. The tool's purpose implies it is for enumerating warehouses, but it does not mention alternatives such as snowflake_describe_warehouse for a single warehouse or snowflake_get_warehouse_load_history for load metrics. The context is inferred but not stated.

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