Score Quiz Question

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

Annotations already signal idempotency, destructive behavior, and open-world semantics. The description adds a useful permission requirement ('Requires grading permissions') and clarifies that the tool targets a single question within a submission, adding context beyond the schema without contradicting the 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?

The description is two sentences, front-loads the main action, and includes only necessary guidance about attempt selection and permissions. No filler or redundancy.

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?

For a mutating, permission-restricted scoring tool, the description covers the key operational details: what action is performed, how attempts are selected, and the permission requirement. It could additionally note that scoring a question likely overwrites any existing question score, but the destructiveHint annotation already signals this.

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 100%, so all parameters are already described in the schema. The description mostly restates the 'attempt' behavior rather than adding new parameter semantics, which matches the baseline for fully documented schemas.

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 identifies the action: scoring a specific question within a quiz submission. This distinguishes it from related tools like grade_submission (which scores an entire submission) and list_quiz_submissions (which reads submissions).

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 gives explicit guidance on how to target an attempt, noting that omitting 'attempt' targets the latest submission. It also states the permission prerequisite. However, it does not explicitly contrast when to prefer this tool over related tools like grade_submission.

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