Download generated screenshots

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

Annotations declare this is not read-only (it writes files to disk) and not destructive, which the description is consistent with. The description adds real behavioral context beyond the annotations: the default output location ~/StoreShots/<jobId> and the 24-hour job expiry, both of which affect invocation.

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?

A single compact sentence front-loads the action, the artifacts, and the destination, with the expiry caveat appended. 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?

For a download tool with no output schema, the description covers what is retrieved, the format options, and where files land. It could mention whether returned paths are reported or how partial failures are handled, but nothing essential to correct invocation is missing.

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?

With schema coverage at 67%, the description usefully restates the format choices (ZIP, PNGs, or both) and clarifies the default local directory, supplementing the schema's terse 'Default zip.' and 'Local directory to save into.' notes.

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 job's ZIP and/or individual PNGs), plus the destination. It implicitly distinguishes itself from generate_screenshots by being the retrieval step, though it does not name any sibling explicitly.

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 24h expiry note gives a useful timing constraint for when this must be called, but there is no explicit when-to-use guidance or routing against alternatives such as generate_screenshots or list_styles.

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