delete_assignment

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states 'This cannot be undone', effectively warning about irreversibility. This is a critical safety-relevant trait for a destructive tool, though it does not elaborate on other effects like cascading deletions.

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 with no filler. 'Permanently delete an assignment' states the action, and 'This cannot be undone' adds necessary warning, both earning their place without 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 simple delete tool with full schema coverage and no output schema, the description covers the essential behavioral context: permanence and irreversibility. It doesn't mention the confirm_name safety check, but the schema documents that. Overall, the context is sufficient for an agent to select and invoke the tool correctly.

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?

The input schema has 100% description coverage for all three parameters (course_id, assignment_id, confirm_name), each with clear definitions. The description adds no additional parameter-level meaning, 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 states 'Permanently delete an assignment' with a specific verb and resource, and 'permanently' adds crucial scope, distinguishing it from update_assignment or other assignment operations. Among sibling delete tools, its target is clearly assignments, making the purpose unambiguous.

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 implies usage when deletion is intended but provides no explicit when-to-use or alternative guidance. It relies on the verb 'delete' and the permanence note to convey context, but does not mention alternatives like update_assignment or the safety confirm_name step.

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