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

With no annotations provided, the description carries the full burden of behavioral disclosure. It details that iOS uses WebKit's dialect rather than full CDP, that Chrome-only domains fail with -32601, and that `*.enable` reports success without proving domain existence. It also specifies the browser-only scope, which prevents misuse on device/native contexts.

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?

Though longer than typical descriptions, every sentence serves a distinct purpose: purpose, scope, parameter format, alternative guidance, and platform-specific limitations. The structure uses a clear 'IMPORTANT, iOS:' label for critical caveats. It is dense but not bloated.

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 complexity (raw protocol access, dual-platform differences, no annotations or output schema), the description covers the essential context: what it does, when to use it, platform-specific failure modes, and scope boundaries. It explains absent domains and the misleading nature of `*.enable` on iOS, which an agent would need to avoid incorrect usage. No critical omission is apparent for making an informed invocation.

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 provides 100% coverage with descriptions for all five parameters, so the baseline is 3. The description adds an example of `method` ('Emulation.setGeolocationOverride') and reinforces that `params` is the command's parameter object, but this largely duplicates schema information. It does not introduce significant new parameter semantics beyond what the schema states.

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 opens with a specific verb+resource: 'Send a raw DevTools-protocol command to the browser page on a device and return its reply.' It positions itself as an escape hatch for capabilities no dedicated tool wraps, listing example domains (Emulation, Performance, CSS, Animation, DOM mutation), which clearly distinguishes it from sibling tools like webpage_click or webpage_evaluate.

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?

It explicitly states 'Prefer a dedicated tool when one exists: they handle setup ordering, lifecycle and teardown that a bare command does not,' giving clear when-to-use vs alternative guidance. It also warns against using `*.enable` as a capability probe on iOS, providing a concrete when-not-to behavior. The scope limitation to the browser (never device/native apps) further clarifies appropriate use.

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