adb_screencap

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

No annotations provided; description only says 'capture screenshot...save to local file'. It does not disclose side effects, overwrite behavior, permissions needed, or constraints.

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?

Description is a single sentence and very concise, but it is under-specified for the tool's complexity. Would benefit from additional context without being verbose.

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, no annotations, and required parameters, the description does not cover return value, error conditions, or file format. Incomplete for a tool with 2 required inputs.

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?

Input schema has 2 parameters with 0% description coverage. Description adds no information about 'serial' or 'output_path' beyond 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?

Description clearly states it captures a screenshot and saves to a local file using exec-out. However, it does not explicitly differentiate from sibling tool scrcpy_screenshot, which also captures screenshots.

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 on when to use this tool over alternatives like scrcpy_screenshot or adb_shell. The description only states the basic action without context.

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