adb_screencap

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

The description states it saves to filesystem and returns the path, but with no annotations, it lacks behavioral details like overwrite behavior, file format, device readiness requirements, or error handling. This is insufficient for a mutation tool without annotation support.

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 extremely concise with no superfluous words. It front-loads the action and includes the key output (file path).

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?

Given the simple nature of the tool, the description covers the essential action and output. However, it lacks guidance on error cases and differentiation from similar tools, which limits completeness in a context with many siblings.

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. The description does not add any additional meaning to the parameters beyond what is in the schema. It mentions the return value but not how parameters affect behavior.

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 captures a screenshot and saves it to the local filesystem, returning the file path. This distinguishes it from adb_ui_dump (which captures UI hierarchy) and adb_screenrecord_start (video), but does not differentiate among sibling screenshot tools like adb_screenshot_compressed or adb_screenshot_baseline.

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 is provided on when to use this tool versus other screenshot-related siblings such as adb_screenshot_compressed, adb_screenshot_baseline, or adb_ui_dump. The agent must infer the appropriate use case from context.

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