flow_browser_generate_video

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

No annotations are provided, so the description carries the full burden. It usefully discloses that this uses a persistent job orchestrator and requires a manually authenticated Google browser session, but it does not explain job lifecycle, waitForCompletion behavior, or return characteristics.

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 two short sentences, front-loads the compatibility-alias role, and contains no filler. It is efficiently structured for scanning.

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 an eight-parameter video-generation tool with no annotations and no output schema, the description is too thin. It mentions orchestration and authentication but omits job behavior, result handling, parameter semantics, and when this alias should be preferred over the primary generate_video 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 description coverage is only 63%, and the description adds no parameter-level meaning at all. Some schema fields such as priority, idempotencyKey, and waitForCompletion lack descriptions, and the prose does not compensate for those gaps.

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 identifies this as a compatibility alias for generate_video and distinguishes it by noting the persistent job orchestrator. The resource is clear from the tool name and the named sibling, though the description never explicitly says it generates a video.

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?

It implies use as a compatibility path for generate_video and states an authentication prerequisite, but it does not clearly say when to choose this over generate_video or when to avoid it. The agent must infer the selection criteria from the alias relationship.

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