run_scheduled_flow

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

With no annotations, the description must convey behavioral traits. It only states that the tool runs a flow and that it does so in dry run mode by default. It does not disclose whether the action is reversible, what side effects occur in a dry run versus actual run, or any permissions needed. This is insufficient for safe usage.

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 very short (6 words) and directly conveys the core action. However, it sacrifices necessary detail for brevity. It is front-loaded with the verb and resource, but additional context is missing.

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 zero parameters and no output schema, the description is incomplete. It does not explain what a 'flow' is, how the tool knows which flow to run, the difference between dry run and actual run, or what the outcome will be. For an action-oriented tool among many CRUD siblings, more context is needed.

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?

There are zero parameters, and schema coverage is trivially 100%. The description does not explain the absence of parameters, which may confuse an agent as to how the flow is identified. Baseline for 0 params is 4, but the lack of clarification reduces the score.

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 clearly states the tool's action 'Run a flow now' and notes the default behavior (dry run). The verb ('run') and resource ('flow') are specific, but it does not specify which flow is being run, assuming context. It distinguishes from sibling tools like list_scheduled_flows and create_scheduled_flow by focusing on immediate execution.

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?

No guidance on when to use this tool versus alternatives. The description mentions 'dry run by default' but does not explain how to perform an actual run or when a dry run is appropriate. No exclusions or prerequisites are provided.

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