lakehouse_delete_shortcut

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

The description is consistent with annotations (destructiveHint=true), but it adds no behavioral detail beyond the annotation—no mention of permanence, permissions, or side effects. Since the annotations already signal destruction, this is acceptable but not enriched.

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?

One short sentence with no filler; the action and target resource are immediately clear. Every word earns its place.

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, the description plus fully documented schema and destructive annotation give an agent enough to call it correctly. It stops short of explicitly noting irreversibility, but this is largely implied by the destructiveHint annotation.

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 all four parameters are already documented with descriptions and an example for shortcutPath. The tool description adds no additional parameter meaning beyond what the schema provides, so it meets the baseline.

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 uses a specific verb ('Delete') and names the exact resource ('OneLake shortcut from a lakehouse'), clearly distinguishing it from related sibling tools like lakehouse_delete, lakehouse_create_shortcut, and lakehouse_list_shortcuts.

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 intended use is implied: call this when a OneLake shortcut needs to be removed. However, it does not explicitly state when not to use it or mention alternatives such as lakehouse_list_shortcuts for discovering shortcuts before deletion.

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