Permanently delete a quiz question using its external unique identifier. Requires user confirmation because this action cannot be undone.
Permanently delete a Quiz question, identified by its external unique question identifier. This cannot be undone, confirm with the user first.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | external unique question identifier |
Changes observed during successful MCP inspections.
v1.1.2Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"v1.0.22Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark destructiveHint=true, but the description adds that the deletion is permanent and cannot be undone, and requires user confirmation. This adds behavioral context beyond the annotations, though it does not elaborate on side effects or error behavior.
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?
Two concise sentences with no filler. The action is front-loaded, followed by irreversibility and confirmation guidance. Every sentence contributes necessary information.
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 one-parameter destructive tool with no output schema, the description covers the core purpose, irreversibility, and user confirmation. There is no missing information an agent needs to call it 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?
Schema description coverage is 100%, so the schema already explains the id parameter. The description does not add any additional parameter semantics beyond what is in the schema, meeting the baseline for high 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 clearly states the verb 'delete' and the resource 'Quiz question', and specifies it is identified by an external unique question identifier. This is specific and unambiguous, distinguishing it from deleting a quiz or other resources.
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 includes an explicit instruction to confirm with the user first, which is important for a destructive action. However, it does not mention when to use this tool versus alternatives like edubase_delete_quiz_questions, so it lacks explicit exclusions or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.