EduBase MCP Server

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

While annotations indicate this is a non-destructive write (readOnlyHint=false, destructiveHint=false), the description fails to mention behavioral traits like the non-idempotent nature (idempotentHint=false) implying duplicate username failures, or side effects such as automatic password generation and email/SMS notifications when the 'notify' parameter is used.

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 the action verb front-loaded. However, extreme brevity comes at the cost of omitting helpful context, preventing a perfect score.

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 tool's complexity (18 parameters with intricate behaviors like template-based creation, group assignment, and timezone configuration), a single sentence is insufficient. The description lacks mention of return values, error conditions (e.g., duplicate usernames), or the existence 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 input schema fully documents all 18 parameters including constraints and defaults. The description adds no additional parameter semantics beyond the schema, meeting the baseline expectation 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?

The description uses a specific verb ('Create') and resource ('EduBase user account'), clearly indicating it creates user accounts. However, it does not explicitly distinguish this from sibling tools like edubase_patch_user (updates) or relationship-management endpoints like edubase_post_user_classes, though the naming convention implies this is the primary creation endpoint.

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_patch_user for updates, nor does it mention prerequisites like administrative permissions required to create accounts.

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