browser_emulate_media

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'emulate media type' without explaining side effects, persistence, or how it affects rendering. It also omits the colorScheme functionality entirely.

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 extremely brief (single phrase), which is concise but under-specified. It earns its place by stating the core action, but lacks the structure to convey additional context expected for a tool with two parameters.

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?

The tool has two parameters, no annotations, and no output schema, so the description should provide adequate context. It only covers the 'media type' aspect and omits 'colorScheme', and gives no hint about when or why to use this tool in browser automation workflows.

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?

Schema description coverage is 0%, so the description must compensate for parameter meaning. It doesn't mention either 'media' or 'colorScheme', leaving the enums to self-explain. The schema is somewhat clear, but the description adds no value in explaining parameter semantics.

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 '模拟媒体类型' (emulate media type) uses a specific verb and resource, indicating the tool's general purpose. However, it doesn't differentiate from other browser tools or mention the colorScheme parameter, leaving the full scope unclear.

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 is provided on when to use this tool versus alternatives, nor are any exclusions or prerequisites mentioned. The description simply states the action without contextualizing it among sibling browser tools.

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