download_images

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

With no annotations, the description carries the full burden. It does disclose real internals — retries, validation, min-size filtering, content-hash dedup — which is more than most. However it never says that files are written to disk, where, or under what permissions/overwrite semantics, so the mutation side effect is left implicit.

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 tight sentences with the core action front-loaded and the behavioral details second. No filler, though the second sentence is a dense list that could be slightly more scannable.

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?

An output schema exists so return values need not be explained, but with zero annotation coverage and zero schema description coverage, the description should compensate more. It omits the output directory semantics (a write target), the items payload format, and concurrency behavior, leaving the agent guessing at the most consequential parameters.

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 0% across 5 parameters, and the description only semantically covers the minimum-size filtering (min_width/min_height) and dedup behavior. It says nothing about the required 'items' shape, output_dir, or max_concurrency, leaving most parameters undocumented in both places.

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?

Clear verb+resource ('Download ranked image candidates') and it explicitly ties its input to the sibling search_images, so an agent can place it in the pipeline. It does not, however, distinguish itself from other retrieval siblings such as fetch_creator_images or inspect_item.

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 'returned by search_images' implies this is the follow-up step after search_images, which is useful implied usage. But there is no explicit when-to-use, no when-not-to-use, and no statement about what to do if the candidate set is stale or needs re-fetching.

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