trigger_cloud_flow

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

Annotations indicate destructive and open world, and the description adds 'executes automation that may modify cloud resources externally', providing additional behavioral context beyond the annotations.

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 concise sentences: first states purpose, second adds behavioral info, third gives negative guidance. Front-loaded and efficient with no redundant information.

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 tool with 2 parameters (one optional object) and no output schema, the description covers purpose, usage boundaries, and behavioral traits. Missing details on return format or error handling, but overall adequate.

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 baseline is 3. The description mentions 'flow ID' and 'any parameters' but adds minimal extra meaning beyond the schema definitions for flowID and requestBodyJson.

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?

Clearly states the tool triggers a CloudFlow workflow by flow ID, distinguishing from viewing definitions or checking available flows.

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?

Explicitly says when to use (to trigger a flow) and when not to use (not for viewing definitions or checking available flows), and advises asking the user to confirm the flow ID and parameters before executing.

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