pause_on_load

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

With no annotations provided, the description carries the full burden and excels by disclosing key behavioral traits: it explains the side effect ('reloads the current page (destructive of unsaved state)'), prerequisites ('requires an active Chrome tab'), and return value ('confirmation of debugger enablement and page reload'). This covers safety, requirements, and output expectations.

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 front-loaded with the core functionality, followed by side effects, prerequisites, returns, usage context, and alternatives—all in a compact, well-structured format. Every sentence adds value without redundancy, making it highly efficient.

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's complexity (involves debugging, page reloads, and side effects), no annotations, and no output schema, the description is complete. It covers purpose, behavior, prerequisites, returns, and alternatives, providing all necessary context for an agent to use it correctly.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds no parameter information, which is appropriate. A baseline of 4 is applied since it doesn't detract from the schema, but it's not a 5 as it doesn't enhance beyond the schema (though none is required).

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's purpose with specific verbs ('Enables', 'injects a breakpoint') and resources ('debugger', 'script loaded after reloading the page'). It distinguishes from siblings by mentioning specific alternatives ('set_breakpoint', 'pause_on_exceptions'), making the purpose unambiguous.

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 explicitly states when to use this tool ('Use this to debug script execution from the page load') and provides clear alternatives ('set_breakpoint for targeting specific scripts/lines', 'pause_on_exceptions for exception-based pausing'). It also includes prerequisites ('requires an active Chrome tab'), giving comprehensive guidance.

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