adb_ci_wait_boot

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

With no annotations, the description carries full burden. It discloses polling behavior and launcher readiness, but does not specify whether it modifies device state, what happens on timeout, or any side effects. More details on error handling or resource usage would improve transparency.

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 efficient sentences: first states primary purpose, second adds key behavioral detail (polling and CI relevance). No filler words, front-loaded with essential 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?

The description is adequate for a simple wait tool but lacks details on return values (e.g., success/failure), error scenarios, or differentiation from similar siblings like adb_ci_device_ready. With no output schema or annotations, additional context would be beneficial.

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 descriptions for both parameters (timeoutSeconds and device). The description adds no additional meaning beyond the schema; it mentions polling but not parameter specifics. Baseline 3 is appropriate as schema does the work.

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 waits for a device or emulator to fully boot, specifying that it polls sys.boot_completed and launcher readiness. This is a specific verb-resource pair, and it distinguishes from siblings like adb_ci_device_ready by emphasizing the waiting and polling mechanism.

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 labels it 'Essential for CI pipelines' but does not explicitly state when to use it versus alternatives like adb_ci_device_ready or adb_wait_stable. No exclusion criteria or when-not-to-use guidance is provided.

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