EduBase MCP Server

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable domain context by explaining the exam-quiz hierarchy relationship and clarifies the scope limitation to 'owned and managed' exams, which is not captured in annotations.

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?

Two sentences with zero waste: first establishes purpose, second provides necessary domain context about hierarchy. Information is appropriately front-loaded with the action verb leading.

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 presence of an output schema, readOnly annotations, and 100% parameter coverage, the description successfully provides sufficient domain context (hierarchy explanation) without needing to detail return values. Minor gap in not explicitly contrasting with singular get_exam.

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 is 3. The description does not add parameter-specific semantics, syntax details, or usage patterns beyond what the schema already documents for search, active, limit, and page parameters.

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?

Description provides specific verb 'List' + resource 'exams' and clearly defines scope as 'owned and managed.' The additional sentence explaining 'Exams are the highest level in the EduBase Quiz hierarchy' effectively distinguishes exams from quizzes and implies this is a collection endpoint (vs. singular edubase_get_exam).

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?

While the description implies this lists multiple exams via the plural naming and 'List' verb, it lacks explicit guidance on when to use this versus edubase_get_exam (singular) or edubase_get_exam_results_user. No 'when-not' or alternative tool references are provided.

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