delete-quiz-question-group

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

The destructiveHint annotation is present and matches the 'Delete' wording, but the description adds no further behavioral disclosure. It does not say whether deleting the group also deletes its questions, whether the operation is irreversible, or what permissions are required—important details for a destructive action. This is a clear gap beyond what the annotation already provides.

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 a single, front-loaded sentence with no unnecessary words. It immediately states the action and target, making it easy for an agent to process.

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?

The operation is simple and all parameters are well-defined, but the description leaves ambiguity about the relationship between a question group and its questions: does deletion cascade to contained questions? This is a meaningful context gap, though for a basic delete operation with a destructiveHint annotation it is minimally viable.

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?

All three parameters (courseId, quizId, groupId) are fully described in the input schema with 100% coverage, so the schema carries the parameter semantics. The description does not add parameter details, which is acceptable given the high schema coverage.

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 is a clear, specific statement: 'Delete a question group from a quiz.' It names the action (delete), the resource (question group), and the parent context (quiz), and it can be distinguished from sibling tools such as delete-quiz-question or delete-quiz.

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 clearly implies the appropriate context: use this tool when a question group needs to be removed from a quiz. It doesn't explicitly mention alternatives or when-not-to-use, but the resource-specific wording provides sufficient guidance for this simple CRUD operation.

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