previewapk_record_download

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

With no annotations, the description carries the behavior burden and does add real value: it discloses that transfers are resumable from the interruption point and that omitting rec_id falls back to the session's latest finished recording. It omits overwrite behavior when the file exists, size limits, and permissions.

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?

Two sentences, zero filler, with the action and destination front-loaded and the resumability/default notes following in a natural order.

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?

No output schema or annotations exist, so the description must stand alone; it covers the save target and resumability but leaves the device parameter, overwrite semantics, and behavior when no recording is available unaddressed.

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 67%; path and rec_id are already documented in the schema. The description adds the nuance that rec_id defaults to the session's *latest finished* recording, but the device parameter is unexplained in both schema and description, so it doesn't compensate fully.

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?

States a specific verb (download) and resource (a finished recording's MP4) plus the destination (local file path), which cleanly separates it from sibling record_start/record_stop and the screenshot/observe tools.

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 phrase 'finished recording' plus the omission rule for rec_id gives clear context for when to call it, and the schema note ties rec_id to record_stop. It stops short of explicitly naming record_stop as the prerequisite or stating what to do if no finished recording exists.

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