eduframe-mcp

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

Annotations already establish this is read-only, idempotent, and non-destructive. The description adds minimal behavioral context beyond stating the scope ('all' records), but does not mention pagination mechanics, rate limits, or what constitutes a 'course location record'.

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 five words. While efficient, it borders on underspecified given the lack of output schema and pagination details. It is appropriately front-loaded but could benefit from one additional sentence on pagination.

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?

Without an output schema, the description should explain what a 'course location record' contains or what the return structure looks like. It also omits pagination behavior, which is critical for a 'list all' style endpoint. The description is too minimal for the tool's complexity.

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 parameters (cursor, per_page) are fully self-documenting. The description adds no supplemental parameter information, but given the complete schema coverage, this meets the baseline expectation.

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 uses a clear verb ('Get') and resource ('course location records'), distinguishing it from the singular 'get_course_location' sibling via the plural form and word 'all'. However, it loses a point for not clarifying whether this retrieves every record in one call or requires pagination to get the full set.

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 no guidance on when to use this tool versus 'get_course_location' (singular) or other location-related tools like 'get_meeting_locations'. It also fails to mention that pagination is required to retrieve the complete dataset.

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