eduframe-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether this operation is idempotent, what happens if the user_id doesn't exist, whether it sends notifications, or what the return value indicates.

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?

While appropriately brief at three words, the description is under-specified rather than efficiently informative. The single sentence does not earn its place by delivering actionable context beyond the function name.

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 single-parameter tool without output schema or annotations, the description remains insufficient. It omits the critical domain relationship that teachers are created from existing users (implied by the user_id parameter but never stated), leaving ambiguity about the tool's exact function in the user management workflow.

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 for the single user_id parameter, the baseline score applies. The description adds no additional parameter context (e.g., explaining that this converts an existing user rather than creating a new account), but the schema adequately documents the parameter.

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 'Create a new teacher' essentially restates the tool name (tautology) and fails to distinguish from siblings like create_teacher_role, create_teacher_enrollment, or activate_teacher. It does not clarify whether this creates a new user account or promotes an existing user to teacher status.

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 alternatives like activate_teacher (for reactivating) or create_teacher_enrollment (for assigning to courses). No prerequisites mentioned, such as whether the user_id must already exist via create_user.

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