download_material

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

With no annotations, the description carries the full disclosure burden. It reveals that the tool downloads a file to the local downloads folder, which implies a write operation. However, it omits details like file overwrite behavior, failure handling, permission requirements, or whether the download is synchronous. The extract_text note is useful but the description falls short of explaining side effects or the operational context beyond the basic action.

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 concise, with two sentences. The primary action is front-loaded, and the explanation of extract_text is placed after the main action, which is logical. Every sentence earns its place, and there is no redundancy or filler.

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 the tool's simplicity (two parameters, no annotations, no output schema), the description covers the essential purpose and one parameter. However, it lacks details on return values, error behavior, or any operational side effects. For such a straightforward tool, this is adequate but leaves room for improvement, especially since behavioral transparency is low.

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?

The schema description coverage is 0%, so the description must compensate. It explains extract_text well, stating that it pulls readable text from PDFs for summarization. It does not explain material_id, but that parameter's name and context make its purpose self-evident. The description adds meaning for one parameter but leaves the other implicit, providing partial compensation for the coverage gap.

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 clearly states the action (download), the resource (one material), and the destination (local downloads folder). This distinguishes it from sibling tools like list_materials and get_assignment, which respectively list and retrieve details rather than download. The 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 does not explicitly state when to use this tool versus alternatives or provide exclusions. It implies usage by naming the action, but there is no guidance on when one might choose this over listing materials or other tools. The mention of extract_text for PDFs gives some context but not a clear decision framework.

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