emulate

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

With no annotations, the description carries the full behavioral burden. It discloses only one trait – persistence until debugger detach – and omits whether settings are destructive, how they interact/override each other, permission requirements, and what state changes on the page.

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 short, front-loaded sentences with no padding. However, the first sentence's vagueness means the brevity stems partly from under-specification rather than efficient communication.

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 an 8-parameter mutation-style tool with no annotations and no output schema, the description is too thin. It neither enumerates the emulatable features nor describes the return/effect, leaving most of the agent's decision inputs to the 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?

Schema description coverage is only 63%, and the description adds no parameter meaning at all – "various features" does not map to viewport, userAgent, geolocation, or the throttling/network options. The 37% undocumented gap is left entirely to the schema.

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 names a verb ("Emulates") and a resource ("features on the page"), but "various features" stays vague and largely restates the tool name rather than enumerating what can be emulated. An agent can't tell what specifically this covers without opening the schema.

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 when-to-use guidance and no alternatives are named. The second sentence ("Settings last until the debugger detaches") is a behavioral note, not usage direction, so nothing routes the agent between this and siblings like cdp or resize_page.

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