execute_workflow

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

No annotations are provided, so the description carries the full behavioral burden. It never says whether the execution is synchronous or asynchronous, whether the call returns an execution ID, whether it is idempotent, or what permissions/rate limits apply — all critical for a mutation trigger.

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 front-loaded sentence with no filler, though it is arguably too terse for a mutation tool and leaves room for one more sentence of substance.

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 side-effecting trigger with no annotations and no output schema, the description omits what the agent most needs: whether execution is async, what gets returned, and how failures surface. The schema covers inputs but nothing covers behavior.

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% and both parameters are documented in-schema, so the baseline of 3 applies. The description adds nothing about the shape or expected content of the optional 'data' object for the 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 states a specific verb and resource ('trigger a workflow execution') and the word 'Manually' usefully separates it from the sibling activate_workflow/deactivate_workflow toggles. It does not explicitly name an alternative tool, so it stops short of the 5-tier sibling differentiation.

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?

There is no guidance on when to prefer this over activate_workflow, nor any prerequisites or conditions. 'Manually' hints at a contrast with scheduled/automatic runs, but the agent must infer that.

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