pause_on_load

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

No annotations are provided, so the description carries the full burden. It explicitly discloses the destructive side effect ('reloads the current page (destructive of unsaved state)'), prerequisites, and the return value. This is more than sufficient for an agent to understand the tool's behavior and risks.

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 well-organized into distinct clauses: purpose, side effects, prerequisites, return, usage, and alternatives. Every sentence provides essential information without redundancy, and the primary purpose is front-loaded. It is efficient despite covering multiple aspects.

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 there is no output schema, the description compensates by stating the return value ('confirmation of debugger enablement and page reload'). It covers prerequisites, side effects, usage, and alternatives, leaving no critical operational detail missing. For a tool with only optional parameters and clear behavior, this is 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 description coverage is 100%, meaning both parameters (tab_id and instance_id) are already fully described in the schema. The description adds no additional parameter-specific meaning, so it meets the baseline expectation but does not exceed it.

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 specific action: 'Enables the debugger and injects a breakpoint at the first statement of any script loaded after reloading the page.' It also distinguishes itself from siblings by explicitly naming alternatives, so an agent can immediately tell it apart from set_breakpoint and pause_on_exceptions.

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?

It explicitly states when to use the tool ('Use this to debug script execution from the page load.') and provides alternative tools with their different purposes ('set_breakpoint' for targeting specific scripts/lines, 'pause_on_exceptions' for exception-based pausing). It also mentions the prerequisite of an active Chrome tab, giving complete usage context.

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