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

All annotations are negated hints (readOnly=false, destructive=false), so the description carries the burden of behavioral disclosure. It only adds the ambiguous term 'interactive' without explaining lifecycle, blocking behavior, or prerequisites, which is insufficient for a create operation.

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 10-word sentence that is front-loaded with the verb and contains zero filler. It communicates the core action efficiently without redundancy.

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 output schema and parameter descriptions cover return values and inputs well. However, the description fails to explain the 'interactive run' concept and its relationship to workflow_runs_execute_step, which is essential context for a moderately complex tool with nested object inputs.

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 100% with clear per-parameter descriptions, so the baseline applies. The tool description mentions 'workflow and optional inputs' but adds no semantics beyond what the schema already documents.

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 a specific verb ('Create') and resource ('interactive workflow run'), which clearly distinguishes it from siblings like workflow_runs_get and workflow_runs_execute_step. However, the term 'interactive' is not elaborated, leaving some ambiguity about what makes this run type distinct.

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 provides no guidance on when to use this tool versus alternatives such as workflow_runs_execute_step, nor does it explain when an interactive run is appropriate. No exclusions or alternative tools are mentioned.

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