warehouses_delete

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

Description adds minimal value beyond annotations (destructiveHint=true, readOnlyHint=false). It says 'permanently', which is implicit from 'delete', and does not disclose potential failure conditions or side effects.

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?

Description is one sentence, no fluff. Efficient, but could be slightly improved by including a usage note without becoming verbose.

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 simple single-parameter tool, the description is adequate but lacks usage context. It does not mention destructive nature beyond 'permanently delete', but annotations already cover that.

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 100%, so baseline is 3. The description does not add extra meaning beyond the schema's 'SQL warehouse ID' for the only parameter.

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?

Description uses clear verb 'Permanently delete' and specific resource 'SQL warehouse', distinguishing it from sibling tools like warehouses_create, warehouses_edit, warehouses_start, etc.

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 guidance on when to use this tool, prerequisites (e.g., warehouse must exist, must be stopped?), or alternatives. The description is a single statement without context.

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