debug_highlight

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

No annotations are provided, so the description must fully convey behavior. It says 'highlight' but does not explain how the highlighting is rendered (e.g., CSS outline, background color change, temporary overlay), whether it persists, or if it can be reverted. This lack of detail impairs an agent's understanding of side effects.

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, efficient sentence that conveys the core functionality. However, it could be slightly more informative without losing conciseness, such as mentioning the optional color parameter.

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 simplicity and lack of output schema or annotations, the description is minimally adequate but leaves gaps: it doesn't specify the visual effect of highlighting, duration, or interaction with other tools. An agent would benefit from knowing that highlighting is non-persistent and used for visual debugging.

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?

Both parameters are already well-described in the schema (selector: 'CSS selector', color: 'Highlight color' with default). The description adds no additional semantic meaning beyond the schema's coverage, which is 100%, earning a baseline score of 3.

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 action: highlighting elements by selector. It uses a specific verb ('highlight') and resource ('elements matching a selector'), and is distinct from sibling tools like dom_find_element (which finds without highlighting) or debug_screenshot (which captures image).

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 guidance on when to use this tool versus alternatives like dom_find_element or debug_set_viewport. The description does not specify use cases or context, nor does it mention any prerequisites or limitations.

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