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

Annotations already cover the mutation/safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description adds one genuine behavioral trait beyond them: assignment consumption ('uses an included assignment when grading starts unless the account has unlimited assignments'). It adds little else about permissions or side effects, so a middling score is appropriate.

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?

Three tight sentences with the core purpose front-loaded, followed by input modes and quota/return notes. No filler, though the mention of return id partly duplicates the output schema.

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 tool with a nested prompt object and an existing output schema, the description adequately covers purpose, accepted input forms, quota behavior, and return. The main gap is that it does not position this step relative to start_grading or the import tools.

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 80%, so the baseline is 3. The description goes further by clarifying the mutual exclusivity of the two question sources ('Accepts a Fiveable FRQ or SAQ id, or the teacher's own question in prompt'), which the schema alone does not state, adding real meaning to fiveableQuestionId vs prompt.

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 (Creates) and resource (grading session) with scope qualifiers ('for finished student work, including paper, Google Docs or an AP Classroom export'). It implicitly separates itself from start_grading by noting the session is used 'when grading starts,' though it never names the sibling explicitly.

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?

Context is implied ('for finished student work') but the description gives no explicit when-to-use versus alternatives such as import_essays_from_files or start_grading. The agent must infer that this is the prerequisite step before grading begins.

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