eduframe-mcp

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

While annotations correctly indicate this is read-only and idempotent, the description adds no behavioral context beyond what the name implies. It fails to disclose that results are paginated (requiring cursor management), what the default page size is, or how the 'published' filter affects the result set.

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 (four words), which avoids verbosity, but it is under-specified for a tool with pagination and filtering capabilities. The single sentence does not earn its place effectively because it lacks critical operational context.

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 pagination parameters (cursor, per_page) and a filter (published), the description is incomplete. It should explain the pagination pattern and filtering behavior. With no output schema provided, the description misses the opportunity to clarify the return structure (list of records).

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, published). The description adds no additional semantic information about these parameters, meeting the baseline expectation when the schema is self-documenting.

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 records'), but it is essentially a tautology of the tool name 'get_courses'. It fails to distinguish from the sibling tool 'get_course' (singular) or clarify whether this returns a list versus a single record.

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 'get_course' or other course-related tools. There is no mention of pagination strategy (cursor parameter) or when to apply the 'published' filter versus retrieving all courses.

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