adb_screenshot_baseline

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

The description discloses that it saves to a 'baselines directory', which is a behavioral trait. However, it does not mention potential overwriting behavior, permissions required, or any side effects beyond saving. Given no annotations, this is minimal disclosure.

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?

The description is two sentences, front-loaded with the primary action and purpose. Every word adds value, and there is no redundancy. It is appropriately sized for the tool's simplicity.

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 with 4 parameters and no output schema, the description is mostly complete. It lacks explanation of how baselines are used (e.g., comparison workflow), but the sibling tools fill that context. Minor gap: no mention of file format or storage location details.

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 the schema already documents all parameters with detailed descriptions. The description adds minimal extra meaning (e.g., 'baselines directory', 'for later comparison'), which is not essential beyond the schema.

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 action ('Capture a named screenshot baseline'), the resource ('screenshot baseline'), and the purpose ('for later comparison'). It distinguishes from sibling tools like adb_screencap and adb_screenshot_diff by specifying the naming and comparison intent.

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 creating baselines but provides no explicit guidance on when to use this tool versus alternatives (e.g., adb_screencap for simple captures). No exclusions or when-not-to-use advice is given.

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