Diff against a checkpoint

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

The description adds a significant behavioral detail beyond the annotations: the note about the next browser_verify baseline becoming the current state. This is not covered by readOnlyHint or destructiveHint, so the description meaningfully increases transparency.

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 two sentences, clear and to the point, with the important note placed at the end. It is concise without unnecessary detail.

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?

The description provides the core purpose and a key side effect, but lacks explanation of the 'name' parameter and does not specify output format. Given the absence of an output schema, the description is adequate but not fully complete for unassisted understanding.

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 schema covers only sessionId with a description; the required 'name' parameter has no explanation. The description does not clarify what 'name' refers to (presumably the checkpoint name), leaving ambiguity. With only 50% schema coverage and no supplementary explanation, parameter semantics are insufficient.

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 that the tool diffs the current state against a checkpoint saved with browser_checkpoint. It is specific enough to distinguish from browser_checkpoint and browser_assert, though it does not explicitly name siblings.

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 gives a useful note about the next browser_verify baseline becoming the current state, but it does not explicitly state when to use this tool versus alternatives. The guidance is implied rather than explicit.

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