EduBase MCP Server

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

While annotations indicate destructiveHint=true and idempotentHint=true, the description adds minimal behavioral context. It does not clarify what 'archive' implies versus 'remove', whether the operation is recoverable, or what happens to associated data like exam results, certificates, or questions. The idempotent nature is not explained.

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?

At only three words ('Remove/archive exam.'), the description is excessively terse for a destructive operation with ambiguous semantics. The brevity creates uncertainty rather than clarity, failing to earn its place as adequate documentation.

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 this is a destructive operation with no output schema, the description should clarify the archive vs. delete semantics and data retention implications. The current description leaves critical behavioral questions unanswered, making it insufficient for safe tool invocation.

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 ('exam identification string'), the schema sufficiently documents the parameter. The description adds no additional parameter context, meeting the baseline expectation when schema coverage is high.

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 action (Remove/archive) and resource (exam), but the 'Remove/archive' phrasing creates ambiguity about whether this performs a hard delete or soft delete/archive. It fails to distinguish this tool from siblings like edubase_delete_exam_branding or edubase_delete_exam_users that delete specific exam components rather than the exam itself.

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 versus related tools. Given the presence of sibling tools for deleting specific exam aspects (permissions, tags, users, branding), the description should clarify that this targets the exam entity itself, but it does not.

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