Save Screenshot

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

Annotations indicate readOnlyHint=false, so the write behavior is already implied. The description adds only that the output is 'to a file', which is also reflected in the saveTo parameter. It does not disclose overwrite behavior, required permissions, or side effects beyond what annotations already convey.

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 a single concise sentence with no redundant or unnecessary wording. It is front-loaded with the action and target, making it easy to scan.

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 two-parameter tool with strong schema coverage, the description is mostly adequate. However, it misses an opportunity to clarify when to use save versus take_screenshot, and the phrase 'to a file' leaves ambiguous whether the path is on the device or the host. These gaps prevent full contextual completeness.

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 description coverage is 100%; both device and saveTo have clear descriptions, including how to discover devices and the required filename extensions. The tool description itself adds no additional parameter meaning, so the baseline score of 3 applies.

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 states a specific verb ('save'), a resource ('screenshot of the mobile device'), and a destination ('to a file'). This clearly communicates the core operation, though it does not explicitly distinguish itself from the closely related sibling mobile_take_screenshot.

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 provides no guidance on when to use this tool versus alternatives. Given that mobile_take_screenshot is a sibling, the absence of any comparison or selection criteria leaves the agent to infer the distinction from the tool name alone.

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