EduBase MCP Server

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable content context that the tool returns both 'questions and question groups' (not just questions), but does not disclose operational details like pagination, rate limits, or cache behavior.

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 well-structured sentences with zero waste: the first defines the operation and scope, the second provides essential domain hierarchy context. Every word earns its place without redundancy.

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 single-parameter read operation with an output schema present, the description is appropriately complete. It clarifies the domain model (quiz vs exam hierarchy) and content scope (including question groups), though explicit sibling differentiation would strengthen it further.

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 'quiz' parameter is well-documented in the schema as 'Quiz identification string'. The description references 'Quiz set' which reinforces the parameter's purpose, but adds no syntax or format details beyond the schema baseline.

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 action ('List'), resource ('questions and question groups'), and scope ('in a Quiz set'). It distinguishes from exam-related siblings by clarifying the quiz/exam hierarchy, though it doesn't explicitly contrast with singular 'get_question' or generic 'get_questions' tools.

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 helpful domain context that quizzes are used by exams, implying this tool is for accessing quiz content rather than exam content. However, it lacks explicit 'when to use' guidance or named alternatives compared to siblings like 'get_question' or 'delete_quiz_questions'.

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