eduframe-mcp

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

Annotations already declare readOnlyHint=true and idempotentHint=true, establishing the safety profile. The description adds no behavioral context beyond this—no information about what data is returned, relationships to courses, or caching implications. It merely repeats the implied read-only nature of 'Get'.

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 not wasteful, it borders on under-specification rather than elegant conciseness. No structural issues, but the brevity limits informational value.

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 simple CRUD retrieval operation with comprehensive schema annotations and a single parameter, the description is minimally adequate. However, it lacks differentiation from the plural variant and domain context about course variants, leaving gaps in contextual completeness.

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 ('ID of the course variant to retrieve'), the schema fully documents the single parameter. The description contributes no additional parameter semantics, meeting the baseline expectation when schema coverage is complete.

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 a course variant record' largely restates the tool name (get_course_variant) with minimal expansion. While it confirms the action is a retrieval, it fails to distinguish from the plural sibling get_course_variants or explain what constitutes a 'course variant' in this domain.

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 single-record retrieval versus the batch get_course_variants, nor any mention of prerequisites like needing a valid course variant ID. The description offers no decision-making criteria for the agent.

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