adb_screenshot_compressed

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

Without annotations, the description explains key behaviors: returns local file path, dimensions, file size, imagemagick command, and explicitly states that compression is not done on device. However, it omits error conditions or file location details.

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?

Extremely concise: two sentences plus a clarifying parenthetical. Every sentence adds value, no wasted words.

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 no output schema, the description fully explains what the tool returns and the important post-processing requirement, making it complete for usage.

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 schema has 100% parameter description coverage, so the baseline is 3. The description adds no additional parameter information 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 tool takes a screenshot and pulls the full-resolution PNG with metadata for compression, distinguishing it from other screenshot tools like adb_screencap by focusing on compressed output and client-side processing.

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 use for compressed screenshots but does not explicitly provide when-to-use or when-not-to-use guidance, nor does it compare with siblings like adb_screencap or adb_screenshot_baseline.

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