flow_browser_autopilot

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

No annotations exist, so the description carries the full burden, and it does add real value by stating a manually authenticated persistent browser session is required and that password/MFA automation is never performed. It omits other behaviors an agent needs: that jobs are async by default (waitForCompletion=false), whether submission is idempotent via idempotencyKey, and what happens on session expiry.

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 efficient sentences with no waste, but the size reflects under-specification rather than discipline: an agent needs information that simply isn't there, so brevity does not earn full marks.

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?

Eight parameters, no annotations, no output schema, and no param-level detail — the description should at minimum disambiguate the job-submission semantics, the async/wait behavior, and the idempotency contract. Only the authentication constraint is covered.

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 only 63%, and three parameters (priority, idempotencyKey, waitForCompletion) have no schema description at all. The description says nothing about any parameter, so it does not compensate for the gaps — notably the meaning of priority and the idempotency semantics are left undefined.

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 labels the tool a 'compatibility alias for a bounded, persistent Flow video job' but supplies no verb and never says what invoking it actually does (submit a job? resume one? open a session?). With siblings like flow_browser_generate_video, trigger_flow, and create_flow, an agent cannot tell which resource operation this maps to.

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?

'Compatibility alias' hints it exists for legacy callers, but there is no explicit statement of when to prefer this over flow_browser_generate_video or create_flow, and no prerequisites or exclusions beyond the auth note.

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