flow_scan

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

No annotations provided, so description carries full burden. It comprehensively describes behavior: deterministic sequential scanning, explicit outcomes for each page in pages[], deduplication of issues, and that pages are never silently dropped.

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?

Single paragraph, well-structured with purpose first, then behavioral details. Packs much information efficiently, though could be slightly more concise.

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 explains return format (pages[] with explicit outcomes, fix payload etc). Covers deduplication and that each page carries same flags as scan_page. Complete for a scanning 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%, baseline 3. Description adds meaning beyond schema: clarifies startUrl as starting point, autoNavigate as list after startUrl, and maxPages default of 10. Reinforces that autoNavigate is required.

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 clearly states it scans multi-page user journeys, walks URLs sequentially, and returns one consolidated report. It distinguishes from the sibling tool scan_page by explicitly noting it is better for journeys and that for a single page, one should use scan_page.

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 (multi-page journeys like login -> checkout) and when not (single page -> use scan_page). It also mentions that autoNavigate is required and the server is headless, guiding proper usage.

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