Warehouses List Warehouses

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is clear. The description adds useful scope and output-column context (quoted_name, quoted_qualified_name), but does not explain filtering behavior, pagination, or other operational traits.

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 two tightly written sentences with the core purpose front-loaded. The second sentence adds useful output-column context without unnecessary length.

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?

Because annotations cover safety and an output schema exists, the description need not explain return values in full. However, the undocumented pattern parameter and lack of routing guidance to sibling warehouse tools leave meaningful gaps for an agent deciding how to call it correctly.

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?

There is one optional parameter, pattern, with 0% schema description coverage. The description never mentions pattern or explains what matching behavior it controls, so it does not compensate for the schema gap.

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 uses a specific verb and resource: it lists virtual warehouses in the account and names the fields returned (size, state, auto-suspend configurations). It is clearly a listing operation rather than a describe/mutate operation, but it does not explicitly distinguish itself from sibling tools such as warehouses_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?

The description states what the tool does but gives no guidance on when to use it versus alternatives such as warehouses_describe_warehouse or warehouses_get_warehouse_load_history. It also does not explain when the optional pattern parameter should be used.

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