adb_reboot

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

No annotations provided; description only states the effect without disclosing behavioral traits like loss of ADB connection, reboot delay, or authentication needs. Minimal beyond basic action.

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?

Extremely concise one-sentence description that front-loads the action. However, conciseness sacrifices additional context.

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?

Without output schema, no explanation of return values. Missing behavioral outcomes (e.g., device restarts, disconnection). Adequate for a simple reboot but incomplete.

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 descriptions for both parameters. Description adds no extra meaning beyond the schema, so baseline score of 3.

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?

Clear verb 'Reboot' with specific resource 'device' and explicit supported modes (normal, recovery, bootloader). Distinguishes from siblings by focusing on reboot vs. other device operations.

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 like adb_root_shell or adb_restart_app. Does not mention prerequisites or context (e.g., device must be connected).

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