adb_screen

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

No annotations, but description fully discloses behaviors: lock/unlock verify keyguard state via dumpsys window, unlock uses wm dismiss-keyguard, and PIN entry sequence (wake, dismiss, swipe, type, confirm, verify). No contradictions.

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?

Two sentences, front-loaded with purpose, then detailed behavioral context. No redundancy. Efficiently packed with actionable information.

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?

Covers actions, verification, and PIN sequence. Could optionally mention return values or error handling, but sufficient for a control tool with no output schema.

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 covers 100% with parameter descriptions. Description adds value beyond schema by explaining the PIN unlock sequence and verification steps, making usage clearer.

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?

Description clearly states 'Control screen state: wake, sleep, toggle, lock, or unlock' with specific verb and resource. Distinct from siblings like adb_screen_state (read) or adb_screencap (capture).

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?

Provides context for lock/unlock verification and PIN usage, but lacks explicit when-not-to-use or alternatives (e.g., adb_input for custom gestures).

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