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

Annotations declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is already known. The description adds real context beyond that: it runs the latest PUBLISHED revision (not draft), the input envelope is fixed for every run, output is routed per delivery, and the flow must be published first. It stops short of explaining approval/needs_confirmation behavior despite an approvalId parameter, which keeps it from a 5.

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?

Front-loaded with the core action, then usage, then prerequisites, then management siblings. Dense but each sentence carries routing or behavioral information. Slightly long, but no filler.

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 10-parameter mutation with no output schema and an approval flow, the description covers prerequisites, execution semantics, and sibling management well. The notable omission is scheduling cadence detail (time-of-day, timezone, day-of-week) which an agent needs to call this correctly.

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 only 50%, so the description must compensate and it partly does: it clarifies that `input` is a constant envelope matching workbench_flows_run's shape and that `delivery` routes output. However it says nothing about the timing parameters (scheduleTime, scheduleTimezone, scheduleDayOfWeek) or label, leaving half the parameters to bare schema. Baseline 3 given the coverage gap.

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?

States a specific verb+resource ('Set a built flow to run automatically on a cadence') and immediately contrasts it with the nearest sibling ('the deterministic counterpart to a zv1 routine'). An agent can distinguish it from routines_create and workbench_flows_run without opening any schema.

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?

Explicit USE THIS trigger ('run my digest flow every morning') plus an explicit exclusion ('Do NOT create a routine for this'). It also routes the agent to the exact prerequisite and lifecycle siblings: workbench_flows_revisions_list, workbench_flows_publish, workbench_flows_schedules_list/update.

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