EduBase MCP Server

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

The description adds valuable context beyond annotations by specifying 'archive' alongside 'Remove', suggesting a soft-delete or recoverable operation rather than permanent deletion. This nuance complements the destructiveHint=true annotation by clarifying the data retention 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?

Extremely concise at three words. The action is front-loaded and there is no extraneous text, though the brevity borders on under-specification given the destructive nature of the operation.

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?

Adequate for a single-parameter deletion tool with comprehensive annotations and full schema coverage. However, it lacks explanation of the archive mechanism, return behavior, or side effects that would help an agent understand the full operational context.

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?

With 100% schema description coverage for the single 'quiz' parameter, the description appropriately relies on the schema for parameter details and does not need to repeat them. Baseline score applies.

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 the specific action ('Remove/archive') and target resource ('Quiz set'), distinguishing it from sibling tools that delete quiz components (questions, permissions, tags) by specifying the entire 'set' is targeted.

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 no guidance on when to use this tool versus alternatives like 'edubase_delete_quiz_questions' or 'edubase_delete_quiz_tag', nor does it mention prerequisites or recovery procedures.

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