eduframe-mcp

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

No annotations are provided, so the description carries full burden. While 'Create' implies mutation, the description discloses nothing about side effects (e.g., whether teachers are notified, if it creates draft or published states by default), authorization requirements, or error conditions.

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 three words with no waste, but it is under-specified rather than appropriately concise. Given the tool's complexity (15 parameters with type-specific conditionals), this brevity represents inadequate structure rather than efficient communication.

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 complex creation tool with 15 parameters, conditional logic (Fixed vs Flexible types), and nested objects, the description is inadequate. No output schema exists, and without annotations, the description fails to compensate for missing behavioral context.

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 high at 87%, with clear documentation of conditional parameters (e.g., 'Only needed for fixed planned courses'). The description adds no parameter-specific context, but the baseline 3 is appropriate given the schema's quality.

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 planned course' is a tautology that restates the tool name without explaining what distinguishes a 'planned course' from a 'course' (sibling tool create_course exists) or what 'planned' signifies in this domain. It fails to differentiate from siblings.

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 versus create_course, create_program, or create_program_edition. No mention of prerequisites (e.g., requiring an existing course_id) despite the schema showing it as required.

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