download_unsplash_media

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

No annotations are provided, so the description carries the full burden. It discloses a useful side effect ('Creates parent directories automatically') and makes clear this is a disk-writing operation. However, it does not disclose overwrite behavior for existing files, error handling for invalid URLs, or any permission requirements, leaving notable behavioral gaps.

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?

Three sentences, each earning its place: core purpose, input provenance, and a side-effect disclosure. Front-loaded with the primary action, no redundant or filler wording.

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?

This is a low-complexity tool (2 required params, no enums, output schema present), and the description covers purpose, input source, and a side effect. The main gap is overwrite/error behavior for the destination file; with that disclosed it would be a 5.

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%, so the baseline is 3. The description adds value beyond the schema by revealing that URLs should come from search_unsplash_photos, giving the agent provenance guidance for the url parameter that the schema does not include.

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+resource: 'Download a single photo from an Unsplash URL to a local file.' The word 'single' explicitly distinguishes this tool from the sibling download_unsplash_media_batch, and referencing search_unsplash_photos as the URL source further clarifies its role.

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 gives clear context by instructing agents to use URLs returned by search_unsplash_photos (e.g. urls.regular). It implies single-item scope via 'a single photo,' which contrasts with the batch sibling, but it does not explicitly name the batch tool as the alternative or state when not to use this tool.

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