EduBase MCP Server

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

Annotations already declare destructiveHint=true and idempotentHint=true, establishing the safety profile. The description adds no behavioral context beyond these annotations—no explanation of whether this is a hard or soft delete, what happens to associated data (enrollments, submissions), or side effects.

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 brief (two words), which is appropriate for a single-parameter operation, but lacks structural front-loading of critical differentiators needed to distinguish from sibling tools. It is concise but not strategically structured.

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 high density of similar sibling tools (edubase_delete_user_*, edubase_delete_*_members) and the destructive nature of the operation, the description is inadequate. It should clarify that this deletes the user account itself (not just associations) and explain data retention implications.

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 'user' parameter is documented as 'user identification string'), the schema carries the full burden. The description mentions no parameters, but baseline 3 is appropriate given the schema's completeness.

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 'Delete user.' is a tautology that restates the tool name (edubase_delete_user). While it identifies the resource, it fails to distinguish from numerous sibling tools like edubase_delete_user_classes, edubase_delete_user_login, and edubase_delete_user_organizations, which all 'delete user' related resources.

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 provided on when to use this tool versus the many sibling alternatives (e.g., when to delete the user entirely vs. removing them from classes or organizations). No prerequisites mentioned (e.g., whether the user must be deactivated first).

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