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

Beyond the annotations, the description explains important runtime behavior: which node execution starts at and how the payload is exposed to the flow. This adds meaningful context about what happens when the tool is invoked, though it does not mention return behavior or asynchronous execution.

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?

Three short, purposeful sentences. The primary action is stated first, followed by start-node behavior and payload semantics, with no filler or repeated schema content.

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 testing/trigger action, the description covers the core invocation details: what starts, where it starts, and how payload is passed. The lack of any return-value or run-completion information is a minor gap given the tool's purpose, and the schema covers the required parameters.

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 schema already documents all three parameters. The description reinforces the payload-to-{{trigger.*}} mapping that the schema already provides, but adds no significant extra meaning for id or nodeId beyond what the schema states.

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 uses a specific verb ('trigger'), a clear resource ('a flow run'), and a clear intent ('for testing'). It also describes the execution start behavior, which distinguishes it from operations like listing, getting, or canceling flow runs.

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?

The phrase 'Manually trigger for testing' gives clear context for when this tool is appropriate. It does not explicitly name alternatives or exclusion criteria, but the manual-testing framing provides enough situational guidance.

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