turn_on_flow

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Enable flow' reveals no state changes, side effects, persistence semantics, idempotency, or whether the flow must already exist. This is effectively no transparency.

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 only two words, which is under-specification rather than effective conciseness. It does not earn its place because it adds no meaning beyond the tool name and leaves the agent without actionable information.

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?

Even though the tool has only one parameter and no output schema, the description is far from complete. It fails to explain what enabling a flow means, how flowId should be supplied, what prerequisites exist, or what outcome the agent should expect.

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 schema defines only a flowId string with no description and no required flag, and schema description coverage is 0%. The description does not mention the parameter at all, failing to clarify what flowId refers to, where to obtain valid values, or why it is optional.

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 'Enable flow' is a tautology that simply restates the tool name 'turn_on_flow'. It provides no specific definition of what a flow is, what enabling involves, or how this tool differs from siblings like turn_off_flow or validate_flow.

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 guidance on when to use this tool versus alternatives such as turn_off_flow, update_flow, or validate_flow. The description gives no context about prerequisites, sequencing with other flow operations, or situations where this tool should or should not be used.

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