Bulk download PDFs, lab sheets, and other files from a specific SLIIT Courseweb course module by course ID, saving them to a chosen directory.
Bulk download all files (PDFs, lab sheets, etc.) from a specific course module
| Name | Required | Description | Default |
|---|---|---|---|
| courseId | Yes | The ID of the course to sync (e.g. 8805) | |
| outputDir | No | Optional: Directory to save the files. Defaults to ./downloads |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full behavioral burden, yet it omits the key question for a tool named 'sync': whether existing files are skipped, overwritten, or duplicated. It also says nothing about auth/session prerequisites (siblings include set_session_cookie/interactive_login), runtime cost of a bulk download, or rate limits.
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?
One sentence, zero filler, with the operation and target front-loaded. It could have used a few more words to cover sync semantics without becoming bloated.
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?
For a side-effecting download tool with no annotations and no output schema, the description should disclose overwrite behavior and what is returned (count, paths, errors). Those gaps leave an agent unable to predict the effect of repeated invocations.
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% – both courseId and outputDir (with default ./downloads) are fully documented, so baseline is 3. The description's 'PDFs, lab sheets, etc.' describes content types, not parameters, and adds no syntax or format meaning 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 ('bulk download') and resource ('all files ... from a specific course module'), and the 'bulk' wording implicitly contrasts with the sibling download_file (single file). It never names that sibling explicitly, so differentiation is left to inference.
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 use this rather than download_file, scrape_page, or check_module_updates. An agent must guess whether sync means 'fetch only new/changed files' or 're-download everything'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.