Get Download Status

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

Annotations already declare read-only, idempotent, non-destructive, non-open-world behavior. The description adds valuable context beyond that: it returns no file body, it reads only the local cache, and course names come from the local course cache. It does not discuss pagination or freshness/staleness of the cache, which would push it higher.

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?

Front-loaded with the core purpose, followed by the non-return of file contents and the routing to alternatives. Three sentences, each earning its place, though the file-contents caveat is stated twice in slightly different forms.

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?

An output schema exists, so return-value details need not be repeated, and annotations cover the safety profile. Combined with the explicit non-content and local-cache caveats, the description is nearly complete; only cache staleness or refresh behavior is unaddressed.

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% for the single optional course_id parameter, so the schema already documents it. The description adds only the tangential note that course names resolve via the local course cache, not parameter-level detail. Baseline 3 applies when the schema carries the semantics.

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 and resource: it summarizes per-course download status from the MCP server's local cache. It clearly distinguishes itself from file-fetching siblings by stating it does not return file contents.

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?

Explicitly routes the agent: to see file contents, find file_id via eclass_search_downloads/eclass_list_downloads and issue a public URL with eclass_file_handoff. Both the alternative and the condition that selects it are named.

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