eduframe-mcp

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

While annotations correctly declare this as read-only and non-destructive, the description adds no behavioral context about pagination (despite having cursor/per_page parameters), filtering logic, or return format. The 'all' claim contradicts the actual paginated behavior where only 25 items are returned by default.

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 concise at four words, but this represents under-specification rather than efficient information density. The single sentence fails to earn its place by providing substantive guidance beyond the tool name itself.

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 that this is a paginated list endpoint with filtering capabilities and no output schema, the description is incomplete. It should explain pagination behavior, the optional student_id filter, and what constitutes a 'credit record' in this domain.

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 three parameters (cursor, per_page, student_id). The description adds no additional semantic information about these parameters, meeting the baseline expectation when schema coverage is high.

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 credit records' is tautological, essentially restating the tool name 'get_credits'. It fails to distinguish from sibling tools like 'get_credit_categories' or clarify what type of 'credits' these are (academic vs. financial). The claim to get 'all' records is misleading given the presence of a student_id filter parameter.

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?

The description provides absolutely no guidance on when to use this tool versus alternatives, nor does it explain when to use the cursor/pagination versus fetching all results, or how the student_id filter affects behavior.

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