browser_workflow_save

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

No annotations are provided, so the description must convey behavioral traits. It mentions overwrite behavior and that the trace is built from successful calls since session_start, but does not disclose side effects, failure modes, or authorization requirements. Adequate but incomplete.

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 front-load the main purpose and add key details about trace source and overwrite behavior. No wasted words, though slightly more structure would improve scannability.

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?

No output schema exists, so the description should explain return values or success criteria, but it does not. It also lacks prerequisites (e.g., session must be started). Given the tool's complexity and lack of annotations, the description is insufficiently complete.

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 low (33%), with only origin having a description. The description adds context for name and origin by explaining overwrite behavior and stating that origin defaults to first observed origin. However, the optional description parameter is not explained. Partially compensates for schema 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?

Description clearly states the tool persists auto-traced actions as a named workflow for an origin, distinguishing it from other browser_workflow tools like delete, export, run, etc. The verb 'Persist' and resource 'auto-traced actions' make the purpose specific.

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?

The description implies use after starting a session and collecting traces, but does not explicitly state when to use this tool versus alternatives like browser_playbook_save or browser_workflow_export. No when-not-to-use guidance is provided.

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