Download Media

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

Discloses that browser cookies handle authentication automatically, a key behavioral trait. But with no annotations, fails to address potential side effects like file overwriting, disk space usage, or error handling. Moderate added context over minimal structured fields.

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 concise sentences with no redundancy. Front-loaded with verb 'Downloads'. Each sentence adds value: purpose, usage context, authentication advantage.

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?

Given simple two-parameter tool with no output schema, description covers main purpose and usage context. Missing information on return value (e.g., saved file paths) and potential limitations (browser state dependency). Adequate but not exhaustive.

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. Description adds no additional meaning about URL format or output_dir behavior beyond schema descriptions. Merely reinforces surrounding context.

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?

Description clearly states it downloads files from URLs using saved browser sessions. It specifies resource (files) and mechanism (browser sessions). Mentions relationship to auth_fetch, distinguishing from sibling fetch tool. However, lacks explicit differentiation from general download tools or caveats.

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?

Explicitly recommends use for downloading files from auth_fetch results. Highlights automatic authentication as key advantage. No explicit 'when not to use' or alternative tools, but sibling context provides implicit distinction.

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