download_file

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

No annotations are provided, so the description carries the full burden and falls short. It never states that the tool writes to local disk, whether an existing file is overwritten, what authentication is required, or what happens for non-file URLs. Only the schema hints at the destination directory.

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 front-loaded sentence with zero filler; the verb, resource, examples, and required input all appear immediately.

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?

With no annotations and no output schema, the description should explain the tool's side effects and result (e.g., returns a saved file path) and any auth or overwrite behavior. None of that is present, leaving significant gaps for a write-to-disk operation.

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 both url and outputDir are already documented in the schema, making 3 the baseline. The description reinforces that url is a Moodle resource URL and clarifies the file types expected, but adds no format or syntax detail beyond the schema.

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 (file from Courseweb) and clarifies scope with examples (PDFs, lab sheets) plus the required input (resource URL). It does not, however, distinguish itself from a plausible sibling like scrape_page, which could also fetch content from Courseweb.

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 guidance on when to prefer this over scrape_page, nor any prerequisites such as needing an authenticated session first (siblings set_session_cookie and interactive_login suggest auth is a real concern). Usage is only implied by the phrase 'given its resource URL'.

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