fabric_create_dataflow

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

With no annotations present, the description carries the full burden of behavioral disclosure, but it only says 'Create a Dataflow Gen2.' It fails to mention any behavioral traits like idempotency, permissions required, or side effects, making it severely lacking.

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 (one sentence), but it is under-specified and adds minimal value beyond the tool name. It does not earn its place by providing actionable detail; it is more of a tautology.

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 the tool has 3 parameters, no output schema, and empty annotations, the description is grossly incomplete. It does not explain what a Dataflow Gen2 is, what the return value is, or any operational context, leaving the agent unable to fully understand the tool's purpose and usage.

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 coverage is 67% (2 of 3 parameters have descriptions), but the tool description adds no additional meaning beyond what the schema already provides. The 'description' parameter lacks schema documentation and the description does not compensate, leaving the agent with incomplete parameter understanding.

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 'Create a Dataflow Gen2' clearly states the verb 'Create' and the resource 'Dataflow Gen2', distinguishing it from sibling tools like fabric_create_lakehouse or fabric_create_eventhouse. However, it lacks detail on what a Dataflow Gen2 is, which could be more specific.

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 such as fabric_create_item or other create tools. The description does not mention prerequisites, context, or exclude cases, leaving the agent without usage direction.

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