delete_assignment_with_confirmation

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

Annotations already signal destructive and idempotent behavior. The description adds crucial context beyond that: the two-step confirmation flow, permanent cascade deletion of submissions and grades, and admin-dependent recycle-bin retention.

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 tightly packed sentences with no filler. The core action and two-step workflow are front-loaded, followed immediately by the most important consequence: permanent deletion of submissions and grades.

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 destructive, multi-step tool with no output schema, this is complete: it explains the preview/confirm sequence, the permanent cascade, and the recycle-bin caveat. The schema fills in the remaining parameter semantics.

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%, so the baseline is 3. The description references the token flow but does not add meaning beyond what the schema already documents for confirmation_token and the other parameters.

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 states a specific verb and resource: 'Delete an assignment.' It also adds the two-step preview/confirm behavior, which clearly distinguishes it from sibling delete tools aimed at announcements, modules, or pages.

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 procedural guidance: preview first, then confirm with the token. It does not explicitly name alternatives or when-not-to-use conditions, but the workflow is clear enough for correct invocation.

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