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 confirms the destructive nature ('Remove') but adds no further behavioral context about side effects, error conditions (e.g., if the permission doesn't exist), or prerequisites beyond what structured fields provide.

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 is appropriately sized and front-loaded with the action and target. It contains no wasted words, though its brevity leaves little room for critical context that would elevate it to a 5.

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 existence of an output schema and comprehensive annotations, the description meets minimum viability by identifying the core action. However, gaps remain regarding the relationship between this action and member removal, as well as the implications of the idempotent behavior in practice.

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 already documents all three parameters (class, user, permission) including the enum values. The description maps to these parameters but adds no additional semantic details, syntax guidance, or explanations of the permission levels beyond the schema.

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 a specific verb ('Remove') and clearly identifies the resource ('user permission from a class'). However, it does not explicitly differentiate from siblings like 'edubase_delete_class_members' (which removes the user entirely) or explain the distinction between removing a permission versus removing a member.

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. It fails to clarify, for example, that this removes a specific permission level while keeping the user in the class, whereas 'edubase_delete_class_members' would remove the user completely.

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