Submit Assignment File

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

No annotations are provided, so the description bears full responsibility. It discloses the dry-run mode and confirmation requirement but omits details like error handling, file size limits, or behavior when replacing files. Sensible but not exhaustive.

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: first defines purpose and method, second explains the critical confirm behavior and user instruction. No superfluous words, front-loaded with essential information.

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?

With 8 parameters and 0% schema coverage, the description should compensate but only covers two parameters. The output schema exists but the description doesn't leverage it. Lacks completeness for a tool of this 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?

Schema coverage is 0%, yet the description only explains confirm and implicitly file_path. The other six parameters (course, assignment, slot_index, upload_url, allow_replace, slot_description) are not mentioned, leaving the agent without guidance on their usage.

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 action ('Upload a local file'), resource ('Ninova assignment slot'), and method ('official multipart form'). It distinguishes from sibling tools like get_assignment_upload_slots which retrieve slots.

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 states the need for confirm=true for actual posting vs. dry-run preview, and instructs to ask user before confirming. However, it does not mention when to use this tool vs. alternatives like download_resource or read_page.

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