set_flow_dataset

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

With no annotations provided, the description carries the burden of disclosing behavior. It transparently indicates that the operation can either add a new dataset or replace an existing one, but it does not detail side effects, validation behavior, or whether existing data is overwritten without confirmation.

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 a single clear sentence with no redundant wording. It front-loads the action and resource, then provides helpful context about the 'Flow Data' tab.

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 description gives enough context for a typical use case and explains what a flow-data dataset is. It omits return-value details, but there is no output schema and the operation is relatively simple, so the provided context is largely sufficient.

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 low (only project has a description), and the description partially compensates by explaining that value is 'a set of param values' and that the dataset is 'named.' It does not elaborate on the structure or constraints of value, flowId, or name beyond what is inferred from the description.

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 ('Add or replace') and the resource ('named flow-data dataset'), making the tool's purpose unambiguous. It also distinguishes this tool from sibling operations like remove_flow_dataset by mentioning the 'Flow Data' tab context.

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 implies the tool is used for creating or updating flow datasets but does not explicitly contrast it with related tools like set_scenario_dataset or set_variable. The 'Flow Data' tab reference provides some situational context, though not explicit alternative guidance.

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