Execute Workflow

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

With no annotations, the description carries the full burden, and it discloses important behavioral details: the execution goes through the webhook rather than a generic API, the workflow must be active, and data is placed into the workflow's $json.body. It does not cover error handling or permissions, but the primary constraints and side effects are clearly communicated.

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 three focused sentences: the first names the action, the second explains the limitation and activation requirement, and the third explains parameter behavior. There is no filler, repetition, or unnecessary detail.

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?

Given the output schema is present and there are no annotations, the description supplies all essential context an agent needs: what the tool does, its scope and prerequisite, the absence of a generic alternative, and the semantics of data. For a two-parameter tool, this is complete.

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%, so the description must add meaning, and it does. It explains that data is sent as the JSON request body and lands in $json.body, which is not apparent from the schema alone. The optionality of data is conveyed with 'if given,' matching the schema's default null.

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 opens with a specific verb-resource pair ('Trigger a workflow's execution') and immediately narrows the mechanism to a Webhook trigger node. This clearly distinguishes it from workflow CRUD siblings like get_workflow or update_workflow by identifying both the action and its prerequisite.

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?

It explicitly states the key precondition: the tool only works for workflows that contain a Webhook trigger node, and the workflow must be active for the webhook to respond. It also explains the API limitation (no generic 'run workflow by ID' endpoint), setting clear expectations, though it does not enumerate explicit alternatives or when-not-to-use cases beyond that.

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