EduBase MCP Server

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

Annotations declare readOnlyHint=false and destructiveHint=false, indicating a safe write operation. The description adds valuable behavioral context about the data model (independent question existence) but omits details about failure modes, duplicate assignment behavior (despite idempotentHint=false), or side effects.

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 sentence front-loads the core action and targets; the second provides essential data model context. 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 100% schema coverage, present annotations explaining the safety profile, and no output schema, the description adequately covers the tool's purpose, optional grouping behavior, and entity relationships. Minor gap: does not explain what happens on success or non-idempotent duplicate assignment attempts.

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 mentions 'question group' which aligns with the group parameter, but does not add significant semantic detail beyond what the schema already provides for the comma-separated questions format or quiz identification.

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 'Assign' with clear resources 'question(s)' and targets 'Quiz set' or 'question group'. The note 'Questions can exist independently from Quiz sets' effectively distinguishes this from creation tools like edubase_post_question and implies this is a linking operation.

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 implicit usage context by stating that questions can exist independently from quiz sets, guiding the agent to use this for linking existing questions rather than creating new ones. However, it lacks explicit when-to-use guidance or references to siblings like edubase_delete_quiz_questions for removal operations.

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