EduBase MCP Server

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

Annotations cover safety (readOnlyHint, destructiveHint), but the description adds valuable domain-specific behavioral context: it clarifies the ownership scope ('owned and managed') and entity structure ('named collections of questions'), helping the agent understand what data subset is returned without contradicting 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: the first front-loads the action and scope, while the second efficiently provides essential domain context about hierarchy position. Every word earns its place.

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 and comprehensive annotations, the description appropriately focuses on domain context (hierarchy explanation) rather than return values. It adequately covers the tool's purpose and behavioral scope for a listing operation.

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 parameters (search, limit, page) are fully documented in the schema. The description doesn't add additional parameter semantics (e.g., search syntax specifics), meeting the baseline for high-coverage schemas.

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 provides a specific verb ('List') and resource ('Quiz sets'), clearly distinguishing it from sibling tools like 'edubase_get_quiz' (singular) and 'edubase_get_questions' by specifying 'owned and managed' scope and defining what Quiz sets are within the hierarchy.

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 it doesn't explicitly name alternative tools, the description provides clear contextual guidance by positioning Quiz sets as 'the middle level of the EduBase Quiz hierarchy,' which implicitly signals when to use this tool versus those dealing with individual questions (bottom level) or specific quizzes.

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