flow_discover_ui

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

No annotations are provided, so the description carries the burden. It discloses navigation, discovery, and the internal side effect of updating the selectors map. However, it does not mention authentication, error behavior, potential page modifications, or what happens on failure, leaving some behavioral gaps.

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 with no redundant content. The action and purpose are front-loaded, and the secondary effect is stated efficiently.

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 single-parameter tool with no output schema, the description explains the core action and side effect, but does not clarify what the agent receives upon success or failure, nor any error handling. It is adequate but leaves room for more detail.

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?

The input schema already fully documents the sole 'page' parameter with a description and default value. The tool description adds limited extra meaning beyond implying navigation to that page, so baseline 3 applies due to high schema coverage.

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 defines the action (navigate and discover) and the resource (Google Flow page), and distinctly differentiates itself from siblings by mentioning the internal selectors map update. Sibling tools like flow_generate_image or flow_download_latest have clearly different purposes.

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?

Implies usage for preparing robust automation, but does not explicitly state when to use this tool over alternatives or mention any exclusions. The phrase 'for robust automation' gives context but lacks direct guidance on when to invoke it versus other flow tools.

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