수업자료 다운로드

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

Beyond annotations, the description discloses the default save location, that the path is reported back, and that target_dir is restricted to subfolders of the default download folder with outside paths rejected. This is useful behavioral context, though it does not mention overwrite behavior or what happens if both cm_id and file_url are provided.

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 compact and front-loaded: it states the destination and result first, then the required input condition. Every sentence adds useful information without redundancy.

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 tool with no output schema, the description adequately explains the outcome (saved locally and path returned). It covers the key input constraint and directory restrictions. It could be slightly more complete by noting how to obtain cm_id or file_url (e.g., via get_course_materials), but this is not essential for correct invocation.

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 the baseline is 3. The description adds meaningful context beyond the schema by explaining the default folder pattern (~/Downloads/jbnu-lms/<course name>/), that cm_id or file_url are alternatives, and that target_dir cannot escape the default folder. This helps the agent understand parameter relationships.

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 the action (saving course material files locally), the destination folder, and the result (returning the path). It identifies the resource as course material, but does not explicitly distinguish itself from sibling get_course_materials beyond the download/save focus.

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 implies usage for saving files to the local Downloads folder and explains that either cm_id or file_url is required. However, it does not explicitly state when to prefer this over sibling tools like get_course_materials, nor does it mention exclusions such as only being useful for local storage needs.

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