eduframe-mcp

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the action ('Enroll') but does not clarify if the operation is idempotent, what data is returned (no output schema exists), or what side effects occur (e.g., notifications sent, validation rules).

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 consists of a single efficient sentence with no redundant words. However, given the presence of similarly-named sibling tools and the mutation nature of the operation, it may be overly terse rather than appropriately concise.

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 annotations and no output schema, the description should explain the operation's effects and return behavior. It lacks information about what constitutes a successful enrollment, error conditions, or the relationship to the optional 'teacher_role_id' parameter.

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 parameters are fully documented in the schema itself. The description does not add syntactic details or semantic context 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 ('Enroll') with clear resource ('teacher') and target ('planned_course'), establishing what the tool does. However, it fails to differentiate from the sibling tool 'create_teacher_enrollment_by_planned_course_id', which appears to offer similar functionality.

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 (particularly 'create_teacher_enrollment_by_planned_course_id'), nor does it mention prerequisites such as whether the teacher or planned course must exist beforehand, or required permissions.

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