edubase_delete_quiz

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

The description discloses two behavioral traits not captured in the annotations: the fallback to archiving when deletion is not allowed, and the requirement to confirm with the user first. Annotations already indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=true, but the description adds meaningful context about the conditional behavior (archive vs. delete) and the user-confirmation step. This adds value beyond the structured metadata without contradicting it.

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 extremely concise: two short sentences that front-load the primary action ('Delete a Quiz set') and immediately follow with the key fallback and the confirmation requirement. Every word earns its place; there is no fluff or redundancy. It is well-structured for an agent to parse quickly.

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?

Given the tool's simplicity (one parameter, no output schema) and the annotations covering destructive/read-only/idempotent behavior, the description is fairly complete. It explains what the tool does, the fallback behavior, and the confirmation requirement. It does not describe the return value or post-deletion effects, but with no output schema, that is not required. It also doesn't explain how to obtain the quiz ID, but that is presumably available from other tools (e.g., edubase_get_quiz). Overall, the description is adequate for an agent to 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 schema describes the single parameter 'quiz' as 'Quiz identification string', which is minimal but sufficient given 100% schema coverage. The tool description does not add any additional parameter semantics, such as format, how to obtain the ID, or expected values. Since the schema already covers the parameter, a baseline of 3 is appropriate; the description adds no extra value for this dimension.

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 tool's primary function: 'Delete a Quiz set', with a specific resource (Quiz) and a clear verb. It also mentions a fallback action ('or archive it when the user is not allowed to delete it') and a required precondition ('Confirm with the user first'), which distinguishes it from read/update tools like edubase_get_quiz and edubase_patch_quiz. The purpose is unambiguous and specific.

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 provides clear usage context: delete a quiz, with a fallback to archiving when deletion is not permitted, and it explicitly instructs to confirm with the user first. This is a strong guideline for when to invoke the tool. However, it does not explicitly exclude other delete tools (e.g., edubase_delete_quiz_questions) or mention when not to use it, though the tool name largely disambiguates. The confirmation step is a notable usage rule that goes beyond the annotations.

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