kql_database_delete

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds no behavioral context beyond repeating the delete action, such as irreversibility, cascading effects, permissions, or failure conditions. No contradiction exists, but no extra transparency value is provided.

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 declarative sentence with no filler or irrelevant detail. The action and target are front-loaded, making the description maximally concise for a simple deletion tool.

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?

The definition is minimally adequate given the two fully documented parameters and destructive annotation. However, it does not explain what happens on deletion, whether the operation is reversible, error conditions, or what the response/return value indicates, which would improve an agent's confidence in invoking it correctly.

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%, with both workspaceId and kqlDatabaseId documented. The description adds no parameter-specific meaning, so the baseline score of 3 is appropriate because the schema carries the documentation burden.

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 clear action ('Delete') and a specific resource ('KQL database') in plain language. It inherently distinguishes from sibling operations like kql_database_get, kql_database_update, and kql_database_list, since delete is a unique operation for this resource.

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 about when to use this tool, when not to use it, prerequisites, or alternatives. The description merely restates the operation and leaves all contextual decision-making to the agent.

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