adb_mirror_start

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

With no annotations, the description bears full burden. It discloses mode support and session limit but omits behavioral details such as whether it blocks, how to stop, error handling, or impacts on device state (e.g., USB debugging requirement).

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?

Three concise sentences deliver core purpose, prerequisites, and modes. No superfluous information; front-loaded with action.

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 8 parameters and no output schema, the description is too sparse. It fails to explain return behavior, how to end the session (sibling adb_mirror_stop), or error conditions, leaving significant gaps for the agent.

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 coverage is 100% with clear parameter descriptions. The description adds value by mentioning the headless mode but otherwise does not elaborate beyond what the schema already provides. Baseline 3 is appropriate.

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 starts live screen mirroring using scrcpy, specifying supported modes (windowed and headless). This distinguishes it from siblings like adb_mirror_stop, adb_mirror_status, and adb_screenrecord_start.

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 mentions prerequisites (scrcpy installed on PATH) and notes 'One session per device' to manage concurrency. However, it does not explicitly guide when to use this tool versus alternatives like adb_screenrecord_start or how to handle multiple devices.

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