fabric_delete_dataflow

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

The description adds 'Destructive' which is redundant given the annotations already include 'destructiveHint: true'. It fails to disclose additional behavioral traits such as irreversibility, what resources are affected, or any necessary permissions.

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 (two words plus a sentence) with no wasted text, which ensures clarity. However, the brevity sacrifices some contextual detail, but it remains focused and front-loaded.

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 the tool is destructive and has no output schema, the description should at least mention that the operation is irreversible or confirm deletion. It lacks these details, making it incomplete for an agent to fully understand the consequences of invocation.

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?

The input schema already provides descriptions for both parameters (dataflowId and workspace) at 100% coverage. The description does not add meaningful information beyond what the schema offers, so it meets but does not exceed 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 clearly states the verb 'Delete' and the specific resource 'Dataflow Gen2', making the tool's purpose unambiguous. It effectively distinguishes this tool from siblings like fabric_create_dataflow or fabric_run_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?

The description provides no guidance on when to use this tool versus alternatives. It only says 'Destructive', which hints at caution but does not specify conditions, prerequisites, or scenarios where another tool might be more appropriate.

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