inspector_highlight

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

With no annotations, the description must disclose side effects, but it only gives the most basic action and a precondition. It does not mention whether providing a URL triggers navigation, whether the highlight mode changes the session UI, when the mode ends, or what error occurs if no active session exists.

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 a single clean sentence that leads with the primary action and adds the optional-hint qualifier at the end. It is concise and contains no redundant or off-topic details.

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?

For a tool with no annotations, no output schema, and three optional parameters, the description is too sparse to fully model invocation. It leaves unclear whether URL and targetHint combined cause navigation, how highlight mode is exited, and what the tool returns or changes in session state.

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 already covers all three parameters with meaningful descriptions, so the 100% coverage baseline applies. The description's only added phrase, 'optional selector hints,' echoes the targetHint parameter without providing any new style, proof, or interaction guidance.

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 identifies a specific verb ('Activate') and resource ('inspect/highlight mode on an active browser session'), immediately making the tool's purpose clear. It distinguishes itself from siblings like browser_open and task_execute by naming the exact mode it activates.

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 phrase 'on an active browser session' clearly signals that a browser session must already exist, and thereby implies it should be used after browser_open rather than before it. It does not explicitly state when not to use it, but no direct alternative sibling performs a similar highlighting function.

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