edubase_delete_quiz

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

Annotations already indicate destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds 'archive' which may imply a soft delete, conflicting with destructiveHint. No additional behavioral details (e.g., permission requirements, side effects) are provided. The description adds minimally beyond annotations.

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 at two words, but it could be slightly more informative without being lengthy. It is well-structured for a simple tool, though a bit too brief.

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 simple single-parameter tool, no output schema, and present annotations, the description is minimally complete. However, it fails to explain the implication of 'archive' versus 'delete' or any potential consequences, leaving some gaps for an agent.

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 covers 100% of the single parameter ('quiz') with a basic description. The tool description does not add any further parameter-level information, thus meeting the baseline score of 3 for 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 'Remove/archive Quiz set' clearly indicates the action (removal/archiving) and the resource (quiz set), distinguishing it from other delete tools for different entities. However, the use of 'archive' is slightly ambiguous compared to the tool name's 'delete'.

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?

No guidance is provided on when to use this tool versus alternative delete tools (e.g., edubase_delete_quiz_permission, edubase_delete_quiz_questions) or when it should not be used. There is no contextual information to help an agent decide.

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