wake_and_unlock_swipe

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 the main action and the important limitation that it only works without PIN/pattern, but it does not explain failure behavior, whether it errors or no-ops when a secure lock is present, or any device-state prerequisites.

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 definition is a single front-loaded sentence with no wasted wording. The action and the key precondition are both stated efficiently.

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 no-parameter screen-unlock tool with no output schema, the description is mostly complete. It covers the action and the main limitation, though it could say more about the result when the lock screen uses a PIN or pattern.

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 tool has zero parameters, so parameter semantics are not a major concern. The description does not add parameter meaning, but the baseline for a no-parameter tool is 4.

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 states a specific verb and resource: it turns the screen on and swipes up to dismiss the lock screen. It also distinguishes the tool from generic swipe or tap actions by naming the lock-screen dismissal outcome and the no-PIN/pattern scope.

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 gives a clear precondition: it works only without PIN/pattern. That is useful when-not guidance, but it does not name an alternative tool or explicitly say what to do when a PIN or pattern is configured.

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