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

The description discloses that running the workflow actually executes every node, including sends, external writes, payments, and deletes—information that goes beyond the destructiveHint annotation. It also notes that outputs are truncated unless return_output is true.

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 dense but structured with clear sections for side effects, returns, and parameter usage. Every sentence carries operational value, though it is somewhat long.

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?

It covers validation prerequisite, side effects, output format, and parameter details. No output schema exists, so the description adequately fills the gap for a successful execution.

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?

Despite zero schema coverage, the description explains the inputs parameter (simulating form submission/webhook) and the return_output parameter (full outputs vs truncated previews). workflow_id is self-explanatory as the target workflow.

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 'Execute a workflow,' a specific verb and resource. It also distinguishes itself from validate_workflow, making its purpose unmistakable.

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 instructs to run validate_workflow first to catch build errors, and warns against running write/send/payment nodes without user approval, offering clear when-to-use and safety guidance.

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