browser_emulate_media

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

Annotations already signal a non-read-only, potentially destructive operation. The description adds genuine behavioral nuance: omitted parameters are left unchanged, and null clears an override, which clarifies how state mutates and how to reset it. This adds value beyond the annotations without contradicting them.

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 two tight sentences: the first states the tool's purpose with an example, and the second states the omission/null behavior. No filler is present, and the primary action is front-loaded.

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 five optional parameters and complete schema coverage, the description is largely sufficient. It lacks explicit details about persistence scope or how to clear all overrides at once, but the null-clears-override rule and the schema fill most practical gaps.

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 documents all five parameters thoroughly, so the baseline is 3. The description adds a cross-cutting semantic not present in the schema: omitted parameters remain unchanged while null clears an override. This distinction is essential for correct invocation.

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 uses a specific verb ('Emulate'), names the resource ('CSS media features for the page'), and includes a concrete light/dark example. This clearly distinguishes it from the sibling browser tools and tells an agent exactly what domain it operates on.

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 provides important invocation semantics: omitted parameters are left unchanged, and null clears an override. However, it does not explicitly state when to prefer this tool over alternatives, though the unique purpose among siblings makes the intended context largely inferable.

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