process_quiz_attempt

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

Adds substantial value beyond the destructiveHint/non-idempotent annotations: it pins irreversibility to the exact condition (dry_run=False AND finish_attempt=True), flags the tool as UNVERIFIED against a real quiz, and mandates a confirmation step. This is precisely the dangerous-path context the annotations alone don't convey.

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?

Front-loads the critical irreversibility warning and the workflow instruction in a compact form. Minor redundancy ('IRREVERSIBLE...cannot be undone' restated twice), but otherwise tight and well-ordered.

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?

An output schema exists, so return values need no explanation, and the destructive-path behavior is well covered. The only meaningful gap is not contrasting this tool with save_quiz_attempt_responses, which matters given the near-identical sibling.

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 both dry_run and finish_attempt are already documented in the schema. The description's main addition is the combined AND semantics of the two flags for irreversibility, which is useful but largely restates the structured parameter docs; baseline 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?

States a specific verb and resource ('Submit answers for a quiz attempt') and clarifies the final graded submission scope. It does not explicitly differentiate itself from the very similar sibling save_quiz_attempt_responses, so the agent must infer the distinction from the dry_run/finish_attempt workflow.

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?

Gives explicit procedural guidance: call with dry_run=True first, show the preview, and only re-call with dry_run=False after explicit user confirmation. This is strong when/when-not guidance, though it never names the alternative sibling (save_quiz_attempt_responses), leaving the choice between similar tools to inference.

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