ui_run_flow

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention side effects on the browser/session, whether confirmation is required, what the flow execution does, or what success/failure looks like. This is essentially no behavioral transparency.

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 front-loaded sentence with zero wasted words, clearly stating the action and resource. However, its brevity leaves out crucial details, though this is accounted for in other dimensions.

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?

With four parameters, a nested variables object, no output schema, and no annotations, the one-sentence description is completely inadequate. The agent cannot determine how to set confirm, sessionId, or variables, or what the tool returns, making correct invocation unlikely without external knowledge.

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 0%, and the description does not explain any parameter. 'Named' only implies flowName; confirm, sessionId, and variables are entirely unexplained, leaving the agent without guidance for constructing a valid invocation.

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 uses the specific verb 'Run', names the resource type 'UI flow', and locates it in 'ui-definitions/flows.json', clearly distinguishing it from sibling tools like ui_navigate, ui_action, and sf_generate_flow_definition.

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 like ui_navigate or ui_action, nor are prerequisites such as an active session mentioned. The description only states what the tool does, not when to choose it.

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