Get Assignment File

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

Beyond the readOnly/non-destructive annotations, it discloses the dual-mode behavior: an expiring 15-minute browser link under HTTP mode with MCP_SERVER_URL, otherwise a locally saved file path. That is genuinely useful context for a tool whose output shape varies by environment, though it omits any auth/permission requirements.

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, zero waste: the first states purpose and scope, the second states the environment-dependent return behavior plus the input source. Front-loaded and appropriately sized.

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?

No output schema exists, yet the description explains what is returned in both modes (expiring link vs local path), and the schema covers parameter details. An agent has everything needed to call it and interpret the result.

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 80%, so the schema already documents role, file_id, course_id, and assignment_id including the "course_id always required" note. The description only adds provenance guidance (IDs from get-assignment-detail) and nothing about the optional term_id, so it sits at the baseline for high-coverage schemas.

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+resource ("Fetch an assignment file") and enumerates the three file kinds covered. It is clearly distinguishable from siblings like get-assignment-detail (metadata) and get-document-link (course documents).

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?

It tells the agent where to source inputs ("Get file IDs and roles from get-assignment-detail"), which implies the correct workflow order. It does not explicitly say when to prefer this over e.g. get-assignment-submit-link or get-document-link, so no exclusions are stated.

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