grade_student_paper

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

No annotations provided, so description must carry full burden. It mentions optional submission but fails to disclose that the operation modifies existing data, requires permissions, or error cases (e.g., need allow_reopen for submitted papers). Behavioral traits are insufficiently disclosed.

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 a single sentence, extremely concise, but at the expense of essential details. For a tool with 4 parameters and nested objects, it should include more context. It is under-specified rather than efficiently concise.

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 complexity (4 params, nested objects, no output schema), the description is incomplete. It lacks explanation of grading_context, relationship to get_student_grading_bundle, and behavioral notes on submission state and error handling. The parameter descriptions partially compensate but the overview is insufficient.

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 100%, so baseline is 3. The description adds no extra meaning beyond what the schema provides; it does not explain how to obtain or use grading_context despite it being critical. No additional value provided.

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 (batch write scores/comments for multiple questions of a single student) and specifies the optional submission of the whole paper. It uses specific verb (write) and resource (scores/comments), and distinguishes from sibling tool grade_student_question which handles single questions.

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 does not explicitly state when to use this tool vs alternatives (e.g., for batch grading vs single question grading). It also does not mention prerequisites like obtaining grading_context from get_student_grading_bundle, which is required by the schema.

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