scrcpy_start

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

No annotations are provided, so the description carries full burden. It only says 'start screen mirroring', without disclosing whether it runs in background, requires ongoing connection, or has side effects. Behaviors like process lifetime or resource usage are missing.

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 a single short sentence, which is concise and front-loaded. However, it is too brief to be informative; conciseness should not sacrifice necessary detail. For a tool with 2 parameters and no annotations, it is under-specified.

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 no output schema, no annotations, and minimal description, the context is very incomplete. It does not explain return values, error states, prerequisites, or effects. For a tool that starts a potentially long-running process, crucial details are absent.

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%, meaning the input schema has no parameter descriptions. The description does not mention any parameters (e.g., serial required, bit_rate optional). It adds no meaning beyond the schema, failing to compensate for the coverage gap.

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 screen mirroring via scrcpy. It is a specific verb+resource, and among sibling tools like scrcpy_stop and scrcpy_control, it distinguishes as the initiation action. However, it lacks detail on the platform (Android) or what exactly 'screen mirroring' entails.

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 on when to use this tool vs alternatives. For example, it does not mention prerequisites (e.g., device connected, Scrcpy installed) or that this should be used before scrcpy_control. The description provides no context for decision-making.

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