browser_checkpoint

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

Without annotations, the description should disclose behavioral traits like side effects, authorization needs, or whether page state is modified. It only mentions that artifacts are stored under a server-managed directory, leaving important behaviors (e.g., does it pause the page? Is it safe?) unspecified.

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 concise with two sentences, front-loaded with the main action. It avoids unnecessary words, though it could benefit from additional context without compromising conciseness.

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 6 parameters including nested objects and no output schema, the description lacks completeness. It does not explain what artifacts a checkpoint includes, how collectors work, or how this tool differs from similar tools like browser_snapshot.

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 100%, so baseline is 3. The description adds minimal parameter meaning beyond the schema; it does not elaborate on the parameters like 'collectors' or 'fullPage'.

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 tool captures a structured checkpoint for a page or tab and stores artifacts. It is specific about the resource and action, but does not explicitly differentiate from sibling tools like browser_snapshot or browser_checkpoint_report, though the name and context help.

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 provides no guidance on when to use this tool versus alternatives such as browser_snapshot or browser_checkpoint_report. No context about prerequisites, use cases, or when not to use it.

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