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

No annotations exist, so the description carries the full burden and does substantial work: it discloses the LIVE/PAUSED precondition, per-version scoping, deferred effect until start_flow, partial-update semantics for omitted fields, the 30-second default startDate for a new schedule, and that endDate:null clears expiry. It omits permissions/auth requirements and any failure behavior (e.g. what happens if the version is LIVE), which keeps it short of 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 purpose before the conditional rules, and nearly every clause carries load-bearing information (defaults, requiredness, partial-update behavior). It is a single dense paragraph that folds four schedule modes and six special-case rules together, so a bulleted breakdown of the schedule variants would improve scanability without adding length.

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 12-parameter mutation with no annotations and no output schema, the description covers preconditions, defaults, conditional requirements, and partial-update behavior thoroughly. The remaining gaps are the return shape and error conditions, which are the only things an agent could still get wrong.

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?

With 12 parameters at 0% schema description coverage, the description compensates well: it defines the schedule enum, the conditional requirement of everySeconds for "custom", weekDays range 1-7 with 1=Sunday mapping, everyDays/everyWeeks defaults, enabled default true, and the two boolean initiation flags including their dependency. Only versionId and workspaceId go unexplained, which are the two most consequential required inputs for correct invocation.

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 and resource ("Run the whole flow on a clock") and immediately bounds the scope: for a flow without a trigger, and explicitly NOT a polling trigger's frequency. The parenthetical examples ("every morning at 9", "every weekday") make the resource concrete and separate it from the sibling get_flow_schedule, which reads rather than sets.

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?

Gives clear preconditions and context: requires a saved flow version that is not LIVE or PAUSED, and the schedule only takes effect at start_flow. It also notes enabled:false is equivalent to what stop-scheduled-runs does. It never names sibling tools as alternatives (get_flow_schedule, start_flow, pause_flow), so routing to the read-vs-write counterpart is left implicit.

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