eduframe-mcp

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

No annotations provided, yet the description discloses no behavioral traits: it doesn't explain pagination behavior (despite cursor/per_page params), what constitutes 'available', auth requirements, or return value structure.

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?

Single sentence format is appropriately sized and front-loaded, though 'that are available' adds vagueness rather than value. No structural waste.

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?

With numerous location-related siblings and no output schema, the description should explain what planning locations are and how they differ from course/meeting locations. Currently insufficient for correct tool selection.

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?

Schema has 100% description coverage for both parameters (cursor and per_page). The description adds no additional semantics beyond the schema, meeting the baseline for high-coverage schemas.

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?

States 'Get' and 'locations' but 'available' is vague and undefined. With siblings like get_course_locations and get_meeting_locations, the description fails to clarify what distinguishes a 'planning location' or what 'available' means in this context.

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?

Provides no guidance on when to use this tool versus siblings like get_meeting_locations or get_course_locations, nor does it mention prerequisites or filtering capabilities.

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