Submit Assignment File

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

Goes beyond the annotations by disclosing concrete consequences: the instructor sees the file, it consumes a submission attempt, and the action is irreversible unless previewed with confirm=true. The annotations already flag destructiveHint, so the description's added value is the confirm-gate workflow and the 'counts as an attempt' side effect; it says nothing about size limits or failure modes.

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?

Three tight sentences with the purpose and the alternative front-loaded and the irreversibility warning bracketed at the end for emphasis. The bracketed callout is slightly repetitive of the confirm parameter description but earns its place given the destructiveHint.

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?

For a destructive write tool with no output schema, the definition covers the essentials: what is created, who sees it, that it is irreversible, and how to preview safely. Missing only return-value expectations (e.g. whether a submission ID comes back) and file-size/type constraints.

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 coverage is 100%, so every parameter including confirm, comment, course_id, file_path and assignment_id is already documented in the schema. The description reinforces the confirm semantics but adds no format or constraint detail beyond it, which is the baseline-3 case.

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 ('Upload a local file and submit it to an assignment in one step') and immediately distinguishes it from the sibling upload_submission_file. An agent can tell exactly what this does and which tool it is not without reading further.

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?

Names the alternative upload_submission_file and the condition that selects it ('upload now and submit later'), and gives the required two-step preview/confirm procedure. It does not address the other submission siblings (submit_assignment_text, submit_assignment_url), so file-vs-text-vs-URL routing is left to inference.

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