fabric_delete_kql_database

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

The description labels the operation as 'Destructive', which aligns with the annotations' destructiveHint. However, it fails to disclose additional behavioral traits such as whether deletion is permanent, if dependent objects are affected, or what happens to the underlying data. Annotations already provide the destructive hint, so the description adds minimal 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 extremely concise with two short sentences, front-loading the core purpose. Every word is necessary, with no redundancy or extraneous information.

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 that this is a destructive operation with no output schema, the description lacks important context such as irreversibility, impact on dependent items, or typical post-deletion steps. It feels incomplete despite the low complexity, especially compared to sibling tools that often provide more detail.

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% for the two parameters (id and workspace), so the baseline is 3. The description does not add any semantic information beyond what the schema already provides, neither clarifying the parameters nor their expected values.

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 'Delete' and the resource 'KQL database', with 'Destructive' reinforcing the nature. It effectively distinguishes this from sibling tools like fabric_create_kql_database or fabric_get_kql_database.

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 is provided on when to use this tool versus alternatives, nor any prerequisites, permissions, or error conditions. The description simply states what it does without contextual usage advice.

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