activate_workflow

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

With no annotations, the description carries full behavioral burden. 'Activate' is a state mutation, yet the description says nothing about required permissions, idempotency, behavior when already active, or whether the change is reversible. Only the effect ('automatic execution') is conveyed.

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. Every word contributes to the meaning.

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 simple one-parameter mutation the definition is minimally viable, but with no annotations and no output schema it omits what 'automatic execution' entails (triggers/scheduling), error conditions, and its relationship to execute_workflow and deactivate_workflow.

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% for the single workflowId parameter, which the schema already describes as 'The ID of the workflow to activate.' The description adds no syntax, format, or sourcing detail, so baseline 3 is appropriate.

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?

States a specific verb ('Activate') and resource ('workflow'), plus the effect ('start automatic execution'). This subtly distinguishes it from execute_workflow (a one-off run), though it never names the sibling explicitly.

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?

No when-to-use guidance and no reference to alternatives like deactivate_workflow or execute_workflow. The purpose clause hints that it enables automatic execution, but an agent gets no explicit criteria for choosing this over execute_workflow.

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