enable_flow

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

Adds significant behavioral disclosure beyond annotations by stating the tool uses Microsoft's unofficial and unsupported api.flow.microsoft.com endpoint, warning that behavior may change. It also notes the ENABLE_WRITE_OPS=true flag requirement. This is consistent with destructiveHint=true and provides useful risk context.

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 compact and information-dense, covering purpose, parameters, verification, and a caveat in a few short sentences. Slight structural inefficiency exists with the bracketed [DISABLED] note interrupting the flow, but overall every sentence earns its place.

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 two-parameter mutation tool with no output schema, the description adequately covers what the tool does, how to verify success, and a critical risk. It could mention permissions or side effects, but the verification step and endpoint warning fill most gaps.

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 input schema already documents both parameters fully (flow GUID, environment id, with 100% coverage). The description only repeats that flow is required and environment is optional, adding no new semantic detail, so the baseline score of 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?

The description explicitly states 'Turn a flow on' and identifies the exact endpoint (POST .../start), making the tool's function unambiguous. It clearly distinguishes from the sibling disable_flow by indicating the opposite action.

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?

Provides contextual guidance by instructing to verify with get_flow (state -> Started), which implies the appropriate after-action. It does not explicitly discuss when to avoid using it or compare with alternatives, but the enables/disables sibling pair makes the use case sufficiently clear.

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