EduBase MCP Server

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

Annotations declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, covering the safety profile. The description adds no additional behavioral context (such as whether removed users' exam attempts/results are preserved, or if this triggers notifications), but does not contradict the 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 single-sentence description is appropriately front-loaded and contains no redundant or wasteful text. However, it is minimal to the point of being under-specified for a destructive operation, lacking any secondary sentences to clarify behavior or implications.

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 rich annotations and 100% schema coverage, the description is minimally adequate. However, for a destructive tool affecting exam enrollments, it omits important context about what 'remove' entails (unenrollment vs. data deletion) and lacks output information, though no output schema exists to require such documentation.

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, the schema adequately documents both 'exam' and 'users' parameters. The description adds no additional parameter semantics (e.g., examples of ID formats or constraints on the comma-separated list), meeting the baseline for high-coverage schemas.

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 uses specific verb 'Remove' and identifies the resource 'user(s) from an exam', making the basic purpose clear. However, it does not explicitly distinguish this from sibling operations like edubase_delete_exam (which deletes the exam entity) or edubase_delete_exam_permission (which removes permissions rather than users).

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 (such as edubase_post_exam_users to add users), no prerequisites (e.g., whether users must be currently enrolled), and no warnings about irreversibility despite the destructive nature.

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