eduframe-mcp

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

While annotations declare readOnlyHint=true and idempotentHint=true, the description adds no behavioral context beyond the tautology. It does not disclose that results are paginated (despite cursor/per_page parameters), does not explain pagination mechanics, or clarify what 'all' encompasses (historical vs. upcoming).

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 single sentence is front-loaded with the action verb and wastes no words. However, it borders on under-specification given the pagination complexity, leaving the agent to discover cursor behavior solely from the schema.

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 paginated list operation with sorting capabilities and no output schema, the description is insufficient. It fails to prepare the agent for pagination handling, result set limits, or the nature of the returned meeting 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?

With 100% schema description coverage, the baseline score applies. The description does not mention any parameters or add semantic context about the planned_course_id relationship, but the schema fully documents all four parameters including the sort enum values.

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 clearly states the verb (Get) and resource (meeting records) with scope (of a planned course). However, it does not explicitly distinguish from sibling `get_meeting` (singular), which likely retrieves a specific meeting by ID rather than listing all meetings for a course.

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 alternatives. It fails to mention that this is for listing meetings when you have a planned_course_id, or that `get_meeting` should be used when you have a specific meeting ID.

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