EduBase MCP Server

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

Annotations already indicate this is a non-destructive write operation (readOnlyHint=false, destructiveHint=false). The description adds no behavioral context beyond these hints— it does not specify whether the transfer is reversible, if it triggers notifications, or what happens if the exam is already assigned to the user.

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 brief at four words with no redundancy. While it avoids waste, it is arguably underspecified rather than optimally concise—a single additional sentence clarifying the transfer mechanism would significantly improve utility without violating conciseness principles.

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?

Despite simple parameters (2 strings) and the presence of an output schema, the description is incomplete because it fails to define the domain-specific meaning of 'transfer.' For a tool with many sibling transfer operations (class, course, quiz, etc.), the description should clarify whether this assigns, enrolls, or changes ownership.

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?

Schema description coverage is 100%, with both 'exam' and 'user' parameters documented as identification strings in the input schema. The description adds no additional semantic meaning (e.g., expected ID formats, whether these are UUIDs or email addresses), warranting the baseline score 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?

States the verb (transfer) and target resource (exam to user), but 'transfer' is ambiguous in an educational context—does it mean enroll the user in the exam, transfer ownership, or copy the exam to the user's workspace? It does not distinguish from sibling tools like `edubase_post_exam_users` or clarify the transfer directionality beyond the parameter names.

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?

Provides no guidance on when to use this tool versus alternatives such as `edubase_post_exam_users` (which likely adds users to an exam) or `edubase_delete_exam_users`. No prerequisites, exclusions, or contextual triggers are mentioned.

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