set_workflow_active

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

No annotations exist, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether the change is reversible, what permissions are needed, what the confirm parameter does, or what happens to a running workflow when deactivated.

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?

Four words are technically concise, but this is under-specification rather than economy — the single fragment earns its brevity only by omitting everything an agent needs.

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?

This is a state-mutating tool with no annotations, no output schema, and fully undocumented parameters. For that complexity profile the description is completely inadequate; it should at minimum explain the confirm flag and the effect of toggling active.

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% for three parameters, including an undocumented confirm flag whose purpose is entirely non-obvious. The description explains none of active, confirm, or workflow_id, so the agent must guess at the confirm/active interaction.

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?

"Sets workflow active state" largely restates the tool name set_workflow_active rather than defining the operation. It gives a verb and resource but no scope, effect, or distinction from siblings like get_active_state or update_workflow_json.

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 indication of when to call this versus alternatives such as update_workflow_json, rollback_workflow, or get_active_state. No prerequisites, exclusions, or context are provided.

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