eduframe-mcp

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds minimal behavioral context—it claims 'all' records but doesn't disclose that the response is paginated (requiring cursor iteration for complete dataset) or describe response 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 with no redundant words. However, extreme brevity leaves gaps regarding pagination behavior and plural vs singular distinction that could be resolved with one additional clause without sacrificing clarity.

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?

Adequate for a simple list endpoint with good schema coverage, but incomplete given the lack of output schema and presence of closely-named siblings. Missing clarification that this returns a paginated collection rather than literally 'all' records at once.

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 ('Cursor for fetching the next page', 'Number of results per page'), the description doesn't need to duplicate parameter documentation. It meets the baseline expectation for high-coverage schemas without adding supplementary context.

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 specific verb 'Get' with resource 'meeting location records', clearly indicating a retrieval operation. However, it does not explicitly distinguish this list endpoint from the sibling 'get_meeting_location' (singular), which could cause confusion given the similar naming.

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 tool versus alternatives like 'get_meeting_location', nor does it explain when pagination is necessary. The description mentions 'all' but doesn't clarify that results are actually paginated.

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