grade_submission

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the excuse behavior, which is useful, but does not explain whether posting a grade overwrites an existing grade, whether score and grade are mutually exclusive, or what happens if both are supplied. It also does not mention any permission requirements or side effects beyond the action itself.

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 concise and front-loaded. It states the primary action in the first sentence, then provides conditional guidance in the second, and the excuse exception in the third. Every sentence serves a distinct purpose, with no redundancy or filler.

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?

While the description covers the main usage scenarios, it leaves some gaps that could lead to incorrect calls. It does not explicitly state that score and grade are mutually exclusive, nor what the interaction between excuse and other parameters is. Given the presence of an output schema, return values are covered, but for a mutation tool with no annotations, more behavioral context (e.g., overwrite behavior) would be expected for full completeness.

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 description must clarify the parameters. It does this effectively for the ambiguous ones: it explains when to use score (points-based) vs grade (pass_fail, letter_grade, percent) and the semantics of excuse. It also implies comment is optional through 'and/or'. This compensates for the lack of schema descriptions, though it does not explain the identifiers (course_identifier, assignment_id, user_id), which are self-explanatory in an LMS context.

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 opens with a precise verb and resource: 'Post a grade and/or comment for one student's submission on one assignment.' This clearly distinguishes it from bulk grading (bulk_grade_submissions) and rubric-based grading (grade_with_rubric), so an agent can identify the correct tool without inspecting the schema.

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 explains how to choose between score and grade based on assignment type, which is helpful usage guidance. However, it does not explicitly compare this tool to siblings like bulk_grade_submissions or grade_with_rubric, nor state when not to use it. The phrase 'one student's submission on one assignment' implies scope, but lacks an explicit alternative routing.

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