gradescope_get_submission_files

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: signed Gradescope/S3 URLs are intentionally suppressed, which explains an otherwise surprising absence in the response.

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 short sentences, no filler, with the capability stated first and the redirect to the download sibling second. Every sentence 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?

An output schema exists, so explaining return fields is not required, and the description correctly characterizes the payload as safe metadata plus what is excluded. However, for a tool requiring three opaque IDs with no schema descriptions, the definition leaves the agent without enough to supply correct identifiers.

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 0% for all three required parameters (course_id, assignment_id, submission_id), and the description does not explain any of them — not their format, where to obtain them, or how they compose. Only the vague ownership scoping ('authenticated student's submissions') hints at semantics, so it fails to compensate 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?

States a specific verb (get/return) and resource (files in a submission) with a clear scope qualifier ('one of the authenticated student's submissions'). It implicitly separates itself from gradescope_download_submission_file, which is the tool that actually moves bytes.

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: list metadata here, and use gradescope_download_submission_file to retrieve an actual file. It also frames the scoping constraint (only the authenticated student's own submissions), though it does not state exclusions for other list tools like gradescope_list_submissions.

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