Download course

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true; the description adds real value beyond them by explaining that existing files are preserved unless force=true and by enumerating the files written to disk. It does not mention rate limits, auth, or failure behavior for an invalid course code.

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?

Two sentences, both front-loaded with the destination layout first and the overwrite rule second. No filler text.

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 four-parameter download tool with no output schema and solid annotations, the description covers destination, artifacts and overwrite policy. Minor gap: no mention of what happens when the course code is invalid or when transcripts=false.

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 all four parameters are already documented in the schema; the description only reinforces the force/default-keep semantics. Baseline 3 applies since the schema does the heavy lifting.

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), a specific resource (every PDF handout and lesson transcript of a course), the exact destination path (<folder>/risorse/) and the side artifacts (indice.md, corso.json). This is clearly distinguishable from single-item siblings like download, get_lesson and get_transcript.

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 bulk nature of the operation implies when to use it versus the single-file download tools, and the force=true clause tells the agent how re-runs behave. However, it never explicitly names the alternative tools or states when not to use this one.

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