eduframe-mcp

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, establishing this is a safe read operation. The description adds no behavioral context beyond this, failing to disclose that results are paginated, that the default page size is 25, or any rate limiting considerations.

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 a single, efficient sentence with no redundant words. However, it may be overly terse given the complexity of pagination and sibling tool differentiation that should have been addressed.

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 existence of a singular variant endpoint and the paginated nature of this endpoint, the description is incomplete. It should clarify that this returns a paginated collection (not truly 'all' at once) and differentiate from 'get_course_variant'. The lack of output schema increases the burden on the description to explain return behavior.

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 (both cursor and per_page are fully documented), the baseline score applies. The description mentions no parameters, but the schema adequately documents them without needing additional textual support.

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 action (Get) and resource (course variant records), but uses 'all' which is misleading given the pagination parameters (cursor, per_page). It also fails to distinguish from the singular sibling tool 'get_course_variant', leaving ambiguity about when to use the list vs. single-record endpoint.

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 tool versus alternatives. Specifically, there is no mention of the sibling 'get_course_variant' (singular) or when pagination is necessary versus fetching a specific record by ID.

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