warehouse_delete

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the description adds no behavioral information beyond what structured metadata provides. It does not mention whether the deletion is irreversible, whether it removes contained data/tables, or whether any dependencies block deletion—important context for a destructive tool.

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 short sentence with no filler or repetition. It is easy to parse quickly and contains no content that should be moved or removed.

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 simple delete operation with fully documented required parameters and a destructiveHint annotation, the description is minimally adequate. However, it omits any statement of consequences (permanence, cascading deletion), which would make the tool definition complete rather than merely adequate.

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 description coverage is 100%, and the schema already explains warehouseId and workspaceId. The description adds no parameter-level meaning beyond the schema, so it sits at the baseline for schema-documented parameters.

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 specific action ('Delete') and resource ('a warehouse'), so an agent can tell this is the removal operation rather than list/get/create/update. It adds no differentiation beyond the verb+resource pair and essentially restates the tool name, which keeps it at a 4 rather than a 5.

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?

There is no guidance on when to choose warehouse_delete over other warehouse operations or over sibling delete tools for related resources. The agent must infer from the name and schema that this is the deletion entry point.

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