warehouses_create

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

The description only says 'Create a new SQL warehouse. Returns the created warehouse's id.' It does not disclose important behavioral traits like asynchronous creation (even though there is a run_async parameter), potential delays, or permission requirements. Annotations only provide readOnlyHint=false, so the description could add more value.

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 very brief (one sentence) but lacks necessary detail for a tool with 20 parameters. It is not front-loaded with key information, and the brevity comes at the cost of completeness.

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 the tool's complexity (20 parameters, many optional, output schema present), the description is woefully incomplete. It does not explain how to construct a valid request, mention required parameters beyond the schema, or clarify the async behavior. The presence of an output schema does not compensate for the lack of operational context.

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?

With 40% schema description coverage, the description does not add any additional meaning to the parameters beyond what the schema already provides. It does not explain the purpose of optional parameters or how they affect the warehouse creation.

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 clearly states the action ('Create'), the resource ('SQL warehouse'), and the return value (the 'id'). This distinguishes it from sibling tools like warehouses_delete, warehouses_edit, etc., which have different verbs.

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 provides no guidance on when to use this tool, prerequisites, or alternatives. It simply states what it does without context for decision-making.

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