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. It only states 'Get' implying a read operation, but provides no details on error handling (e.g., invalid ID), required permissions, or what data is returned.

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 (5 words, single sentence). While it doesn't waste words, it is arguably under-specified rather than optimally concise. However, every word does contribute to stating the basic purpose.

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 retrieval tool with no output schema and no annotations, the description should do more to clarify the scope (single record vs list) and differentiate from similar siblings. It leaves significant gaps in contextual understanding.

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 parameter 'id' is fully documented in the schema itself. The description adds no additional parameter semantics, which is acceptable given the high schema coverage establishes a baseline of 3.

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 ('program enrollment record'), but it essentially restates the tool name. It fails to distinguish from the plural sibling 'get_program_enrollments' or clarify the difference between 'program_enrollment' and 'enrollment' (siblings 'get_enrollment'/'get_enrollments' exist).

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 lookup versus the plural 'get_program_enrollments' for listing, or versus 'get_enrollment'. No prerequisites or conditions are mentioned.

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