EduBase MCP Server

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

The description confirms the destructive nature of the operation ('Remove'), aligning with annotations.destructiveHint=true. However, it adds no behavioral context beyond the annotations, such as explaining the idempotentHint=true (safe to re-invoke) or what the output schema represents.

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 perfectly concise with zero redundancy. It front-loads the action and target, delivering maximum information density with no extraneous words.

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 rich annotations (destructive/idempotent hints) and an output schema (per context signals), the description provides sufficient context for tool selection. However, it misses the opportunity to mention idempotency or error behavior, which would be helpful for a destructive permission 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 are fully documented in the structured schema (quiz ID, user ID, permission level enum). The description does not add supplementary semantics (e.g., clarifying permission hierarchy or ID formats), warranting the baseline score 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 uses a specific verb ('Remove') and clearly identifies the resource ('user permission from a quiz'). It effectively distinguishes this tool from siblings like edubase_delete_quiz (deletes the quiz itself) and edubase_delete_quiz_tag (deletes tags) by specifying 'permission' as the target.

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 implies this tool is for revocation of access, but provides no explicit guidance on when to use it versus edubase_post_quiz_permission (to add permissions) or edubase_get_quiz_permission (to check existing permissions). No prerequisites or error conditions are mentioned.

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