run-flow

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

No annotations exist, so description must disclose behavior. It only says 'trigger a flow on demand' without detailing side effects, permissions, rate limits, or what happens on failure. Minimal behavioral info beyond the action itself.

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?

Two concise sentences. First states purpose, second provides parameter guidance. No unnecessary words or repetition. Front-loaded and efficient.

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?

Covers purpose and parameter hints adequately for a tool with 3 params and no output schema. However, lacks expected return value (e.g., run ID or status) and error handling notes, leaving the agent slightly uncertain.

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 covers 100% of parameters with descriptions. Description adds value by explaining typical triggerName values and recommending list-flow-triggers for clarity, enhancing understanding beyond schema alone.

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 triggers a flow on demand, using a specific verb and resource. It mentions trigger names but does not explicitly differentiate from sibling tools like enable-flow or disable-flow, though context implies it.

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?

Provides direct guidance on when to use (trigger a flow manually) and includes specific advice on trigger name values ('manual' for button/instant, 'Recurrence' for scheduled). Suggests list-flow-triggers as a fallback, helping agent decide.

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