Workflows: enable

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context whatsoever: it does not say whether enabling is idempotent, whether it fails on an already-enabled workflow, or what side effects (job scheduling, triggers) it starts.

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?

It is two words with zero waste, but the brevity is under-specification rather than disciplined concision. Nothing is front-loaded because nothing is said.

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 state-mutating tool in a large workflow family (create, update, disable, delete, trigger, steps, jobs), a two-word description leaves the agent without the state-transition semantics it needs to invoke this correctly. No output schema exists to compensate, and the description does not fill that gap.

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?

The single parameter has 100% schema description coverage ('Workflow ID'), so the schema carries the meaning. The description adds nothing beyond it, which is the expected baseline when schema coverage is high.

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 is a verbatim restatement of the tool name and title ('workflows_enable' / 'Workflows: enable'), adding no scope, target, or distinction from siblings. It does not differentiate this tool from workflows_disable, workflows_trigger, or integrations_enable, which all act on similar resources.

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 is present: the description never says when an agent should enable a workflow or what preconditions exist (e.g., whether the workflow must be exported/paused first). The natural alternative, workflows_disable, is not mentioned.

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