fabric_delete_lakehouse

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

The annotation already declares destructiveHint=true, so the description's 'Destructive' is redundant. No additional behavioral traits are disclosed, such as whether deletion triggers cascading effects, requires special permissions, or is reversible. Given the annotation covers the destructive nature, a score of 3 is appropriate.

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 extremely short (one sentence) with no wasted words, but it lacks important details that could be added without bloat (e.g., impact of deletion). Conciseness is good but not paired with sufficient informativeness.

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 well-defined parameters and annotations, the description provides the bare minimum. It does not clarify what happens to the lakehouse' contents, whether the operation is synchronous, or what success looks like. With no output schema, the description could have filled this 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 description coverage is 100%, so both parameters are well-documented in the schema. The description does not add any extra meaning or context beyond what the schema provides (e.g., how to find the lakehouseId, the role of workspace). Baseline 3 is suitable.

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 'Delete a lakehouse', which is a specific verb and resource. It is distinct from sibling delete tools that target different resource types, such as fabric_delete_warehouse or fabric_delete_dataflow.

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 vs alternatives. The description does not mention prerequisites, context, or mention other tools (e.g., if user wants to delete a lakehouse with its contents vs just the metadata). Sibling tools include many delete operations, but no differentiation is provided.

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