eduframe-mcp

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It fails to mention pagination behavior, safety characteristics (read-only vs. destructive), or what data structure is returned.

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 brief (4 words), but the single sentence fails to earn its place by delivering useful information beyond the tool name. It is appropriately sized but not effectively front-loaded with critical details.

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 tool with 4 parameters including pagination controls, no output schema, and a complex domain with multiple sibling enrollment-related tools, the description is inadequate. It omits filtering behavior, return value structure, and pagination mechanics.

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?

The input schema has 100% description coverage for all 4 parameters (cursor, per_page, student_id, edition_id). Since the schema already documents the purpose of each parameter, the description meets the baseline requirement despite adding no additional parameter 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 program enrollments' largely restates the tool name (tautology). While 'all' implies a list operation, it fails to distinguish from the sibling tool 'get_program_enrollment' (singular) or explain what constitutes a program enrollment in this domain.

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 'get_program_enrollment' (singular) or 'get_enrollments'. No mention of pagination strategy (cursor-based) or when to apply the optional filters (student_id, edition_id).

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