adb_reboot

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention that rebooting disconnects the adb session, may require reconnect (adb_connect exists as a sibling), that the operation is disruptive/destructive to active sessions, or that bootloader/recovery modes require manual exit. These are significant behavioral gaps for a disruptive operation.

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 single sentence that conveys the core purpose efficiently. No filler, no redundant elaboration. The mode enumeration in the description is useful.

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?

This is a disruptive operation (reboot) with no annotations, no output schema, and ambiguous post-conditions (does the tool wait for reboot completion? does it return immediately? does it need reconnect?). For a 2-param tool, one might argue minimal here suffices, but the disruptive nature and connect/disconnect sibling tooling means the description should clarify expectations about session behavior.

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 50% — the serial parameter has a description but mode does not (though mode's meaning is fairly self-evident from its enum values). The description restates the mode enum values but adds minimal semantic value beyond what the schema's enum already conveys. The serial parameter is explained in the schema, so the description adds nothing new there.

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 verb+resource: 'Reboot the device' with specific modes. It distinguishes from siblings since it's the only reboot-related tool among the adb_* family. Though it names the modes, it doesn't elaborate the purpose of each mode (e.g., recovery vs bootloader), which slightly limits richness.

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 vs alternatives or when not to use it. There are no sibling reboot tools, so a when-to-use note isn't critical, but there's no mention of prerequisites (e.g., device must be connected, reboot disconnects the session) or cautionary notes about interrupting running operations.

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