execute_workflow

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

Annotations already declare destructiveHint=true, so the description's 'may change external systems' is consistent but adds little beyond the annotation. It does add context about 'API-triggered' and 'without input', which are behavioral traits not captured in the schema. However, it fails to mention the confirm parameter or any asynchronous behavior, so the added value is modest.

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 a single, concise sentence that front-loads the action. It avoids fluff and is appropriately short for the operation. However, it lacks critical detail, but that is a completeness issue, not a conciseness one. It earns a 4 for efficient structure.

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 destructive operation with a confirm parameter and an output schema, the description is incomplete. It does not explain the confirm parameter's purpose, what the output contains, or any side effects beyond a vague 'may change external systems'. The presence of an output schema and the destructive nature demand more context than provided.

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 explain parameters. It says 'without input', which is misleading given the schema requires workflow_id and includes confirm. Neither parameter's meaning or the confirm parameter's role is described. The description does not compensate for the lack of schema descriptions.

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 clearly identifies the action (execute) and resource (workflow), and adds scope with 'active API-triggered' and 'without input'. It distinguishes from read-only siblings like list_workflows and get_workflow by implying a state-changing operation, though it does not explicitly name any sibling.

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 offers no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It states the condition 'active API-triggered' but does not explain when to choose it over other tools like cancel_job or list_jobs. No 'when not to use' or alternative routing is provided.

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