Download an eLearn document

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

The description discloses a key behavioral trait: existing files are never overwritten and a numeric suffix is added. This is useful and not covered by annotations (none provided). It also implies the destination is configurable. However, it does not mention error handling, return values, or the exact file naming scheme, but the disclosed behavior is a significant safety-relevant detail.

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 two concise sentences with zero redundancy. The key action and the critical overwrite behavior are front-loaded, and every word earns its place.

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 there is no output schema and no annotations, the description should cover what the tool returns, error conditions, and how IDs are obtained. It only states the action. It lacks crucial information for an agent to confirm success or handle failures, and does not mention whether the download is synchronous or asynchronous.

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 only 25% (only destinationDir has a description). The description does not explain the parameters courseId, topicId, or filename, nor how they relate to the download. It mentions 'configured local download directory' but doesn't clarify that destinationDir is an optional override. The description fails to compensate for the low schema coverage.

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?

The description states a specific verb ('download') and resource ('file topic') and indicates the destination (local download directory). It is clear and distinct from the sibling get/search tools, though it does not explicitly name alternatives. The main gap is that it doesn't mention what a 'topic' is or how to obtain the IDs, but the core purpose is unambiguous.

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 gives no guidance on when to use this tool versus alternatives, nor does it mention prerequisites like authentication (sibling authentications exist) or when not to use it. It is implied that you need courseId and topicId from other tools, but not stated. No exclusions or routing to siblings.

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