graph_execute_flow

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

With no annotations, the description must disclose behavioral traits, but it only covers parameter optionality. It does not mention side effects, authentication requirements, rate limits, or what the tool returns upon execution (e.g., run ID or result). This leaves the agent uninformed about operational consequences.

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 a single sentence that immediately conveys the primary action. It is free of unnecessary words, front-loaded with the key action, and efficiently adds one conditional note. Every word earns its place.

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 the lack of annotations and output schema, the description is insufficient. It does not explain what happens after execution, how to retrieve results, whether the operation is asynchronous, or any required prerequisites. The agent is left with significant gaps in understanding the tool's full behavior.

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 parameters are already well-documented. The description adds only a brief clarification about flowId optionality, which is already implied by the schema. No additional meaning is provided beyond what the schema offers, resulting in a baseline score of 3.

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 verb 'Execute' and the resource 'a deployed Lamatic flow', making the tool's purpose immediately obvious. It also adds a helpful note about flowId being optional in single-flow integrations, which distinguishes it from similar tools like dev_create_flow.

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 description mentions a specific condition (single-flow integration) where flowId can be omitted, but it does not provide explicit guidance on when to use this tool versus alternatives. There's no discussion of prerequisites, failure modes, or comparison to sibling tools like graph_load_project_flows.

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