EduBase MCP Server

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

The description aligns with annotations (destructiveHint: true, idempotentHint: true) by using the verb 'Remove', confirming the destructive nature. However, it adds minimal behavioral context beyond the annotations—such as whether removed users lose access immediately, if they are notified, or whether the operation affects their other organization memberships.

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 of six words with no redundancy. While appropriately front-loaded with the action verb, it borders on underspecified given the destructive nature and lack of output schema.

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?

For a two-parameter deletion tool with robust annotations covering safety profiles, the description is minimally adequate. However, it lacks information about the return value (success indication), error conditions (e.g., if users aren't members), or whether the removal is reversible.

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 ('organization identification string' and 'comma-separated list of user identification strings'), the schema fully documents the parameters. The description adds no additional semantic information about parameter formats or constraints, warranting the baseline score.

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 states a clear verb+resource ('Remove user(s) from an organization') that accurately describes the operation. However, it does not explicitly differentiate from similar tools like 'edubase_delete_user_organizations' (which likely removes a user from multiple organizations) or 'edubase_delete_organization' (which deletes the org itself).

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' (which likely deletes the user entirely) or 'edubase_delete_user_organizations'. It also omits prerequisites such as administrative permissions or the impact on user's historical data.

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