eduframe-mcp

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

No annotations are provided, so the description carries full disclosure burden. It fails to mention mutation effects, idempotency, error conditions (e.g., duplicate enrollment), or whether the operation is reversible. The word 'Enroll' implies creation but lacks safety context.

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 description is efficiently structured and front-loaded with the core action. However, it borders on under-specification given the lack of annotations and presence of sibling alternatives, warranting a slight deduction from perfect conciseness.

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?

As a mutation tool with no output schema, no annotations, and overlapping sibling functionality (create_teacher_enrollment), the description is incomplete. It omits return value details, error scenarios, and the specific workflow context distinguishing this endpoint from alternatives.

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?

Schema description coverage is 100%, establishing a baseline of 3. The description maps 'teacher' to teacher_id and 'planned course' to planned_course_id, but adds no syntax details, validation rules, or clarification about the optional teacher_role_id 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 clearly states the action (enroll), subject (teacher), and target (planned course). However, it does not differentiate from the sibling tool 'create_teacher_enrollment', leaving ambiguity about which creation method to prefer.

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 implies usage context (when you need to enroll a teacher to a specific planned course), but provides no explicit guidance on prerequisites (e.g., teacher must exist) or when to use this specific 'by_planned_course_id' variant versus the generic 'create_teacher_enrollment'.

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