Open a Flow Tools app

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

Discloses important behaviors beyond annotations: cost unknown, potential Veo calls, hands control to human, does not drive forms. Credit balance monitoring noted. No contradiction with annotations (readOnlyHint=false, destructiveHint=true align with description).

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?

Four sentences with no filler. First sentence states primary action, subsequent sentences explain critical requirement and rationale. Efficiently packed with necessary detail.

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 no output schema, description adequately explains behavior and risks. Could briefly mention what happens after app opens (e.g., returns control to human), but current text implies it. Complete for safety-critical tool.

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% with descriptions for both parameters. Description adds crucial context: `app_name` validity (must be from flow_list_apps) and `acknowledge_unknown_cost` must be true with reasoning. Enhances schema meaning.

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?

Clear verb ('Open') and resource ('Flow's Tools-gallery apps') with specific action of handing control to human. Distinct from siblings like flow_list_apps (listing) and flow_generate_video (generation).

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 states requirement for `acknowledge_unknown_cost=true` due to unquoted prices and potential internal Veo calls. Contrasts with blindly driving the app's own form, explaining when not to use it. Provides clear context on charge risk.

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