Grade Submission

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

Annotations already signal idempotent, openWorld, and destructive behavior, lowering the bar for the description. The description adds that grading permissions are required, but it does not elaborate on what destructive means here (e.g., overwriting an existing grade), which is a meaningful gap. There is no contradiction with annotations.

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 short sentences deliver the core purpose and the key prerequisite with no filler. The structure is front-loaded, making it easy for an agent to parse quickly.

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 moderate complexity of grading (destructive, idempotent, permission-sensitive), the description covers the basics but not the consequences of overwriting an existing grade or posting a new one. It is adequate for an experienced agent but leaves out useful behavioral details.

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%, with each parameter already documented in the schema. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 uses the specific verb 'Post or update' with the object 'a grade for a submission,' clearly identifying the action and resource. However, it does not explicitly distinguish this from sibling tools like comment_on_submission or score_quiz_question, so it misses full marks.

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 phrase 'Requires grading permissions' provides a useful prerequisite, and the CRUD-like language implies when this tool should be used. However, there is no explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned, leaving usage only implied.

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