mobile_unlock_screen

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

The description discloses the steps (wake, swipe, enter PIN) but lacks details on failure modes (e.g., incorrect PIN) or prerequisites (e.g., ADB connection). Since no annotations exist, the description should carry more behavioral context.

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?

A single sentence that efficiently conveys the tool's purpose and actions. No filler, front-loaded with the main 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 simple tool with two optional parameters and no output schema, the description is mostly complete but could mention what happens on failure (e.g., if PIN is wrong) or if the screen is already unlocked. It covers the core functionality.

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%, and the description adds no new meaning beyond the schema's parameter descriptions. The phrase 'enters a PIN/password if provided' mirrors the schema. 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 unlocks the Android screen by waking, swiping, and entering a PIN. It specifies the verb 'unlock' and the resource 'Android device screen', distinguishing it from sibling tools like mobile_gesture or mobile_power.

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. For example, it does not indicate that it should only be used when the device is locked, nor does it mention prerequisites like the device being connected via ADB.

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