EduBase MCP Server

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

While consistent with annotations (readOnlyHint: false), the description fails to disclose critical behavioral traits: it omits that the operation is non-idempotent (idempotentHint: false), doesn't clarify whether this adds to or replaces existing permissions, and doesn't mention error conditions (e.g., if permission already exists).

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 single-sentence description is appropriately brief and front-loaded, though it contains minor redundancy ('Create new' where 'new' is implied by 'Create').

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 3-parameter schema with full coverage and existing output schema, the description is minimally adequate, but gaps remain regarding idempotency behavior, permission inheritance/replacement logic, and semantic meaning of permission levels that would help agents handle edge cases.

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 maps to the three parameters (quiz, user, permission) but adds no additional semantic context beyond what the schema already provides, such as explaining the hierarchy or practical differences between 'view' and 'admin' permission levels.

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 'Create' with resource 'permission' and scope 'for a user on a quiz', clearly distinguishing it from sibling tools like edubase_get_quiz_permission and edubase_delete_quiz_permission through the action verb.

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 (e.g., when to update vs create), nor does it mention prerequisites such as whether the user or quiz must already exist before calling this tool.

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