agentic_assist_run

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the run is headless, that it persists flow changes (a mutation), and that it targets the Langflow 1.12.x SSE API. It omits auth requirements, whether existing flow state is overwritten, and what the call returns.

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?

A single tight sentence with the action front-loaded and no filler. Every clause (headless, persist, API version) contributes information.

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 5-parameter mutating tool with no annotations and no output schema, the description is minimal. It states the core effect but says nothing about blocking behavior, error modes, or how the optional flow_id/session_id shape the run, leaving real gaps.

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 every parameter is already documented in the schema. The description adds no meaning beyond that (e.g., how flow_id, session_id, and provider interact), so the baseline 3 applies.

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 names a specific verb (Run) and resource (Langflow agentic assistant) plus a mode (headlessly) and a side effect (persists flow changes). It does not, however, explicitly distinguish itself from the several near-identical siblings (agentic_assist, agentic_assist_stream, agentic_execute), so the agent must infer the difference.

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 word 'headlessly' implies a non-interactive/batch use case, but there is no explicit statement of when to pick this tool over agentic_assist, agentic_assist_stream, or agentic_execute. No prerequisites or exclusions are given, leaving the agent to guess in a crowded namespace.

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