eduframe-mcp

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

Annotations already declare readOnlyHint=true and idempotentHint=true, confirming safe read operations. However, the description adds no context about pagination behavior (cursor-based), default page sizes, or how multiple filters interact (AND logic).

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 four-word description is efficiently structured and front-loaded, but it is underspecified for a tool with 6 parameters and pagination support. It prioritizes brevity over necessary functional context.

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?

Given 6 parameters including cursor-based pagination and multiple filters, the description is incomplete. It lacks explanation of pagination mechanics, filtering logic, or return value structure (no output schema exists to compensate).

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?

Input schema has 100% description coverage for all 6 parameters (cursor, per_page, student_id, planned_course_id, status, with_canceled). Since the schema fully documents the parameters, the description baseline is 3, though it adds no additional semantic context.

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 'Get all enrollment records' essentially restates the tool name (get_enrollments) without clarifying scope. It fails to distinguish from sibling tool 'get_enrollment' (singular) or explain whether this returns a list vs. single record.

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 'get_enrollment' (singular), 'get_program_enrollments', or 'cancel_enrollment'. No mention of pagination requirements or filtering best practices despite having 6 optional parameters.

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