download

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

With no annotations, the description must fully explain behavior. It mentions deduplication ('hasn't already been downloaded') and saving to the file system, but lacks details on file naming, location, overwrite behavior, permissions, error handling, or whether all URLs are downloaded simultaneously.

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 sentence that attempts to cover multiple aspects, but it is somewhat wordy and could be broken into two sentences for clarity. Not overly verbose but not optimally concise.

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?

The tool has no output schema and a complex nested parameter (originalOptions). The description does not explain what the tool returns after download, whether it confirms success, or how it handles the many nested options. Missing information about progress, errors, or side effects beyond saving to file system.

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 100%, so baseline is 3. The description does not add significant meaning beyond the schema; the originalOptions are implied for filename generation but not explained. The individual URL parameters are straightforward based on their names.

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 clearly states it downloads render URLs from Urlbox responses to the user's file system. It distinguishes from the sibling tool 'render' by indicating it operates on previous responses. However, 'that hasn't already been downloaded' is ambiguous and could be clarified.

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?

No explicit guidance on when to use this tool versus alternatives like 'render'. The implication that it is used after a render response is not explicit. No when-not or exclusions provided.

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