eduframe-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate that this is a read-only operation, does not describe the pagination behavior implied by the cursor parameter, and does not mention any rate limits or default sorting of results.

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 at four words. While it contains no wasted text, it is arguably under-specified rather than efficiently concise. However, it avoids the verbosity of unnecessary fluff and front-loads the key verb.

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 the presence of closely named siblings (get_teacher_role singular) and pagination parameters, the description is incomplete. It fails to indicate that results are paginated, does not specify what constitutes a 'teacher role', and lacks any indication of the return structure (list vs single object).

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 both parameters (cursor and per_page), establishing a baseline score of 3. The description 'Get all teacher roles' adds no additional semantic context about the parameters (e.g., when to use the cursor, typical page sizes), but the schema adequately documents them.

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 teacher roles' states the basic action and resource but offers minimal specificity. While the word 'all' hints at a collection/list operation (distinguishing from the singular 'get_teacher_role' sibling), it essentially restates the tool name without clarifying what 'teacher roles' represent or the scope of the retrieval.

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 the singular 'get_teacher_role' or other related tools like 'create_teacher_role'. There is no mention of pagination strategy or when to stop iterating through cursors, despite the presence of pagination parameters.

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