EduBase MCP Server

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

The description aligns with annotations (destructiveHint=true, readOnlyHint=false) by stating 'Remove', but adds no behavioral context beyond what annotations and schema provide, such as idempotency details, error conditions if the permission doesn't exist, or reversibility.

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 front-loaded with the action and contains no redundant words. However, for a destructive operation with three required parameters, it borders on being overly terse rather than optimally informative.

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 adequately covers the basic operation but leaves gaps regarding error handling, side effects, or the specific outcome of the removal operation beyond the obvious state change.

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 schema fully documents the video, user, and permission parameters. The description adds no additional parameter semantics, syntax, or examples beyond the schema definitions, 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 (Remove), resource (user permission), and scope (from a video), clearly distinguishing it from sibling tools like edubase_delete_class_permission or edubase_delete_course_permission by explicitly naming the 'video' resource.

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 usage through the action verb 'Remove' and the tool name convention, but provides no explicit guidance on when to use this versus alternatives like edubase_post_video_permission (to add) or edubase_get_video_permission (to check), nor prerequisites or exclusions.

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