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. While 'Cancel' implies a state change, the description fails to specify whether this is reversible, what happens to existing enrollments/attendees, whether refunds are triggered, or required permissions/authorization levels.

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 extremely brief (4 words) and front-loaded. While no words are wasted, the brevity is excessive given the lack of annotations and behavioral context, preventing a score of 5.

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 cancellation operation (potentially destructive with business impact), the description is inadequate. It lacks explanation of side effects, output behavior (no output schema exists), error conditions (e.g., cannot cancel past courses), or relationships to other planning entities that might be affected.

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 'id' parameter is fully documented in the schema), the baseline score is 3. The description adds no additional context about the parameter (e.g., where to obtain the ID, format examples), but the schema adequately covers the semantics.

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 states the basic action (Cancel) and resource (planned course), but borders on tautology by nearly restating the tool name. It does not clarify what constitutes a 'planned course' in this domain or how it differs from similar cancellation siblings like cancel_enrollment or cancel_program_enrollment beyond the resource name.

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 such as update_planned_course (for modifications) or delete_planning_event (for removal). No mention of prerequisites, side effects, or business rules (e.g., can only cancel future courses).

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