dataflow_create

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

Annotations already indicate a non-read-only, non-destructive operation; the description adds little beyond 'new' and 'workspace'. It does not disclose potential side effects, permission requirements, idempotency behavior, or what happens on duplicate names.

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?

Single sentence, clear, and front-loaded with the key scoping information. There is no filler or redundant explanation.

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 create tool with three flat parameters and no nested objects, the description plus schema is sufficient to invoke it correctly. The lack of an output schema or explicit return-value information is a minor gap but not critical for selecting or calling the tool.

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 workspaceId, displayName, and description are all already documented in the schema. The description does not add parameter-level meaning, but it does not need to because the schema handles it.

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?

States a specific action ('Create'), a specific resource ('Dataflow Gen2 item'), and the target location ('in a workspace'). This clearly distinguishes it from sibling tools like dataflow_get, dataflow_update, and dataflow_delete.

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 phrase 'Create a new...' implies the tool should be used when creating a Dataflow, not when reading, updating, or deleting one. However, it does not explicitly mention alternatives or provide exclusion conditions, leaving usage partly to inference.

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