adb_ci_wait_boot

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

No annotations provided, so description carries full burden. It discloses the polling behavior (sys.boot_completed and launcher readiness) which gives insight into how the tool operates, without mentioning side effects or destructive actions.

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, no wasted words. Front-loaded with main purpose, then specifics on behavior and 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?

For a simple waiting tool, description is complete. No output schema, but return behavior is implied (success/timeout). Adequate for an agent to understand the tool's function and parameters.

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%, so baseline is 3. Description does not add meaning beyond schema for timeoutSeconds and device. The mention of polling hints at how timeout is used, but not explicitly.

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 the verb 'wait for a device or emulator to fully boot' and specifies the resource. It distinguishes the tool's purpose from siblings like adb_ci_device_ready by mentioning polling sys.boot_completed and launcher readiness.

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?

Description says 'Essential for CI pipelines' which implies when to use, but does not explicitly state when not to use or mention alternatives. Among siblings, there is adb_ci_device_ready, but no differentiation is provided.

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