eduframe-mcp

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's burden is lower. The description confirms the read-only nature with 'Get', but fails to disclose pagination behavior or typical result set sizes despite having cursor-based pagination parameters.

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 (three words) with no redundant or filler text. However, it may be overly terse given the presence of pagination and filtering capabilities that could benefit from brief mention.

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?

Given the simple parameter structure (3 optional primitives), good annotations, and high schema coverage, the description is minimally adequate. However, it lacks mention of pagination mechanics or filtering behavior, which would be helpful given the lack of an output schema.

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 schema fully documents cursor, per_page, and meeting_id. The description adds no additional semantic meaning, but meets the baseline expectation for high-coverage schemas. The word 'all' slightly conflicts with the filtering capability implied by meeting_id.

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 verb ('Get') and resource ('attendance records'), but the word 'all' is misleading given the meeting_id filter parameter exists. It does not distinguish from the sibling tool 'set_attendance' or clarify whether this retrieves records for all meetings or a specific one.

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, nor does it mention the pagination parameters (cursor, per_page) or when to apply the meeting_id filter versus retrieving unfiltered results.

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