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 explain pagination behavior, the effect of combining filters, or what constitutes a 'teacher record'. No mention of rate limits, permissions, or response format.

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 terse (4 words), which avoids verbosity but underserves the tool's complexity. The front-loaded claim of 'all' records contradicts the filtering capabilities documented in the schema, creating potential confusion rather than clarity.

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 list endpoint with 5 parameters supporting pagination and multiple filter types, the description is insufficient. Without an output schema or annotations, the description should explain the return structure, pagination mechanics, or filtering behavior—none of which are present.

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 parameters are well-documented in the schema itself. The description adds no specific parameter guidance (e.g., explaining that 'search' performs text filtering or that 'cursor' enables pagination), meriting the baseline score for high schema coverage.

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 verb and resource ('Get' + 'teacher records'), but the term 'all' is misleading since the tool supports filtering parameters (id, label_id, search). It also fails to distinguish from sibling 'get_teacher' (singular) or other teacher-related list tools like 'get_planning_teachers'.

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 is provided on when to use this bulk endpoint versus 'get_teacher' (singular) or other teacher-related tools. The description does not mention pagination requirements despite having cursor/per_page parameters, nor when filtering is preferable to fetching 'all'.

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