Warehouses Describe Warehouse

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only that the call reports 'running state' and that names must match exactly; it says nothing about behavior on an unknown name (error vs. empty) beyond what annotations carry.

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?

Two short sentences with the purpose front-loaded and the naming constraint second. Slightly cryptic phrasing ('quoted_name') but no wasted text.

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?

For a read-only describe tool with an output schema and one required parameter, the definition covers purpose, the returned aspect (running state), and the exact-name requirement. Error behavior on a bad name is the only notable gap.

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 coverage is 0%, so the description carries the burden for the single parameter and does so: warehouse_name must be an exact match and must be supplied in double quotes, with the source being a list row's quoted_name. That is real meaning beyond a bare 'string' in the schema.

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 what is returned ('details and running state'), which clearly separates it from warehouses_list_warehouses, warehouses_create_warehouse, and warehouses_drop_warehouse. It never names a sibling explicitly, so differentiation is by implication rather than instruction.

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 mention of a 'list row's quoted_name' implies you obtain the name from warehouses_list_warehouses first, which is a useful usage cue. However, it gives no explicit when-to-use/when-not guidance and says nothing about alternatives such as warehouses_get_warehouse_load_history or warehouses_resize_warehouse.

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