Get Course Resource / File

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

Annotations indicate readOnlyHint and openWorldHint; the description confirms read-only and adds details: redirect handling, cookie authentication, return metadata, inline text for text/PDF with truncation, and file saving behavior. No contradictions.

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 a single paragraph with front-loaded purpose and key details. It is concise with no redundancy, though could be slightly more structured with bullets for clarity.

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?

Return values are described (metadata, file path/size, text extraction) but unclear for binary non-text files without save_to. No mention of error handling or authentication requirements beyond cookies. Adequate but with gaps given complexity.

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?

With 0% schema description coverage, the description partially compensates by explaining cmid/url identification and save_to disk saving, but fails to detail parameters like base_url, session_id, and cookies beyond a mention. Some parameters remain unexplained.

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 tool fetches a Virtuale file/resource by cmid or URL, with specific behavior like following redirects. While it doesn't explicitly distinguish from sibling 'virtuale_list_course_files', the action of fetching a single resource vs listing is evident from context.

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 provides guidance on when to use save_to (for full file) vs inline text, but does not explicitly compare with alternative tools or state when not to use this tool. No exclusions or prerequisites mentioned.

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