break_on_xhr

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

Discloses that v1 fires only if DevTools is open and M3 RDP wires the actual pause, but no annotations are provided, leaving other behaviors (e.g., side effects, removal) unmentioned.

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?

Two efficient sentences, but the second sentence on version details could be more relevant to the core action.

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?

Missing details on hook installation side effects, removal method, and return value; insufficient for a 1-param side-effect tool with no output schema.

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 does not clarify what format urlPattern expects (regex, substring, exact match); with 0% schema description coverage, the parameter remains ambiguous.

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 it installs a hook that issues `debugger;` when an XHR/fetch URL matches a pattern, distinguishing it from sibling tools like set_breakpoint and remove_xhr_breakpoint.

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?

No explicit guidance on when to use this tool vs alternatives; mentions version differences but lacks context for selection or exclusion.

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