tool_upload_submission

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a write operation ('Upload') and includes a 'confirm_write' parameter as a safety measure, but doesn't disclose permissions needed, rate limits, whether uploads are reversible, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is inadequate.

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?

The description is efficiently structured with a clear purpose statement followed by a bullet-point-like parameter list. Every sentence serves a purpose, though the parameter explanations could be more detailed. It's appropriately sized for a 5-parameter tool.

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?

Given the tool's complexity (write operation, 5 parameters, no annotations) and the presence of an output schema (which reduces need to describe returns), the description is minimally adequate. It covers the core action and parameters but lacks behavioral context, usage guidelines, and detailed parameter semantics, leaving gaps for the agent.

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%, so the schema provides no parameter documentation. The description adds basic semantics by listing parameters with brief explanations (e.g., 'List of absolute file paths to upload'), but doesn't elaborate on formats (e.g., what constitutes a valid course_id) or constraints (e.g., file size limits). It compensates partially but not fully for the schema 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?

The description clearly states the action ('Upload files') and target ('as a submission to a Gradescope assignment'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'tool_get_assignment_submissions' or 'tool_get_student_submission', which are read operations versus this write operation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing course/assignment access), exclusions, or comparisons to sibling tools like 'tool_assess_submission_readiness' or 'tool_export_assignment_scores'. The agent must infer usage from the purpose alone.

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