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

Beyond the destructive/idempotent/openWorld annotations, the description discloses the validation and keyword-conflict check with its error code, the plan-limit failure mode, the activation side effect for never-live flows, and the exact events fired (flow.published, flow.activated). That is a genuinely complete behavioral profile for a mutating operation.

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 definition is front-loaded with the core action, then side effects and error codes, with no filler sentences. It is dense but slightly overpacked in the middle where the activation and plan-limit clause runs long.

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 single-parameter destructive mutation with no output schema, it covers errors, side effects, events, and body shape. The only gap is that it does not indicate what a successful response contains, though the absent output schema makes that a minor omission.

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 coverage is 100% so the baseline is 3, and the description adds real value by specifying 'Send {} as the body', clarifying that the required id is supplied outside the request body despite being listed in the input schema. That resolves a genuine ambiguity an agent could otherwise get wrong.

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 opens with a specific verb+resource ('Publish a flow draft') and immediately defines the outcome ('Makes the draft the live definition (new version)'), which implicitly separates it from siblings like update_flow or activate_flow. It never names an alternative explicitly, so the boundary with activate_flow is inferable rather than stated.

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 publishing also activates a flow and the plan-slot condition (403 plan_limit_reached), plus the validation gate (422 invalid_definition). There is no explicit 'do not use this when…' or a named alternative such as activate_flow, so it stops short of full routing guidance.

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