adb_screenshot_baseline

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

No annotations are provided, so the description must fully convey behavioral traits. It states saves to a baselines directory but omits details like whether it overwrites existing baselines, requires permissions, or has side effects. The write operation implications are understated.

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 concise sentences efficiently convey purpose and behavior. No redundant words or filler. Front-loaded with the key action and purpose.

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 tool, the description lacks completeness. It does not clarify the optional nature of the device parameter (only name is required). It fails to specify behavior on name collision (overwrite vs. versioning). Missing details on metadata saved and how baselines are used for comparison.

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?

The input schema already describes both parameters with 100% coverage (name with examples, device as serial). The description adds no new meaning beyond the schema, merely echoing 'named' for the name parameter. Baseline score of 3 is appropriate.

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 tool captures a named screenshot baseline for later comparison, distinguishing it from other screenshot tools like adb_screencap or adb_screenshot_diff. It specifies the action (capture), resource (screenshot baseline), and purpose (comparison).

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 implies usage for later comparison but does not explicitly state when to use this tool over alternatives or when to avoid it. No mention of naming conventions or prerequisites for baseline comparison. Lacks explicit context for selection among sibling tools.

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