EduBase MCP Server

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

The description aligns with the destructiveHint=true annotation by stating 'Remove', but adds no further behavioral context beyond annotations. It does not describe idempotency implications (covered by annotation), error conditions (e.g., if users aren't enrolled), return values, 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 a single, efficient sentence with zero waste. It is appropriately front-loaded with the action verb and contains no redundant or filler text.

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 simple 2-parameter structure, complete schema coverage, and rich annotations (destructive, idempotent hints), the description is sufficient for tool selection and invocation. However, it could be improved by briefly noting the return value or success behavior given the lack of an output schema.

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 baseline is 3. The description confirms the plural nature of the operation ('user(s)') which aligns with the comma-separated format of the 'users' parameter, but adds no syntax details, format examples, or semantics beyond what the schema already provides.

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') with clear resource ('user(s)') and scope ('from a class'), precisely matching the tool name and distinguishing it from siblings like 'edubase_delete_class_permission' (permissions vs members) and 'edubase_delete_organization_members' (different resource scope).

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_delete_user_classes' (user-centric removal) or versus removing class permissions. It also fails to mention the complementary 'edubase_post_class_members' tool or prerequisites like requiring valid class/user IDs.

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