browser_playbook_import

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

With no annotations provided, the description must bear the full burden of behavioral disclosure. It mentions overwriting and rewriting origins, but fails to explain side effects (e.g., whether existing playbooks are replaced without confirmation), validation behavior, permission requirements, or error handling for invalid inputs.

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 consists of two short sentences that efficiently convey the core action and optional behaviors with no redundant words. It is front-loaded with the primary purpose.

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 the tool has 5 parameters, no annotations, no output schema, and involves a complex import operation, the description is insufficient. It lacks details on return values, error states, prerequisite conditions (e.g., file format, URL accessibility), and the exact impact of the overwrite and rewrite flags.

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 description adds meaning to all five parameters by mapping source names to param keys (bundlePath for local file, bundleJson for inline JSON, url for URL) and explaining overwrite and rewriteOrigin with an example. However, it does not clarify that the three source parameters are mutually exclusive.

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 the action ('Import a playbook bundle') and lists three source options (local file, inline JSON, or https URL), distinguishing it from sibling export tools. However, the term 'playbook bundle' is not defined, leaving some ambiguity about the expected format.

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 does not provide guidance on when to use this tool versus alternatives like browser_playbook_save or browser_playbook_propose_update. It mentions optional overwrite and rewrite but gives no context on prerequisites or exclusions.

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