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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely new behavioral context beyond them: the workflow runs autonomously on its schedule and publishes without further confirmation, which is the key consequence an agent cannot infer from structured fields. It omits what happens if the workflow is already running, but the autonomy/publishing trait is well disclosed.

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?

Three short sentences, zero waste. The core action and its ongoing consequence are front-loaded, and the routing hint to stop_workflow ends the description.

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, open-world mutation with a single fully documented parameter and no output schema, the description supplies the consequence of starting (autonomous publishing) and the safe alternative. The only gap is behavior when the workflow is already active, which annotations mark non-idempotent but the description never explains.

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 the schema already explains that the id may be a workflow id or a name as list_workflows shows it. The description adds nothing about the parameter, so the baseline 3 applies.

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 and resource ('Turns a workflow on') and immediately defines its persistent nature: it runs to schedule and publishes without asking again. This distinguishes it implicitly from run_workflow (one-off execution) and explicitly from stop_workflow, so an agent can route correctly without opening schemas.

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?

Names the alternative explicitly ('Use stop_workflow to pause it') and provides an approval prerequisite ('make sure the user has seen what it does'), which tells the agent when this is appropriate. It stops short of an explicit when-not clause or mentioning run_workflow for one-off execution, but the operational context is clear.

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