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

With no annotations, the description carries the behavioral burden; it discloses that activation makes the flow process triggers in production and that keyword conflicts with other published flows surface as advisory warnings to relay. It does not cover edge cases like idempotency, permissions, or behavior when the flow is already active, but the core state change and warning surface are stated.

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 terse, front-loaded sentences: main behavior, invocation examples, and lookup guidance. No filler and no repetition of schema fields.

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?

Given a low-complexity tool with only two params and no output schema, the description covers what it does, how to identify the target, and what to relay to the user. It omits only secondary operational details such as return values and handling of an already-active flow, which are not required for correct selection and invocation.

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 has 0% coverage and both params are optional, so the description must add meaning; it does so by telling the agent to identify the flow by flowName and explicitly saying no id lookup is needed. This effectively documents flowName as sufficient and flowId as unnecessary, though it does not describe formats or when flowId might still be preferred.

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 uses an explicit verb and resource: 'Publish (activate) a flow so it processes triggers in production', and anchors it with natural-language examples ('turn on the welcome DM'). It is clearly distinct from siblings like deactivate_flow and publish, so selecting it doesn't require 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?

It gives clear context for when to invoke: when a flow should go live in production, and supplies example utterances. It also includes one exclusion, 'its name is enough, no id lookup,' but does not explicitly contrast with alternatives such as deactivate_flow or update_flow, so it falls short of a full when/when-not guide.

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