EduBase MCP Server

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

While annotations declare readOnlyHint=false and destructiveHint=false, the description adds no behavioral context beyond this. It fails to explain the idempotentHint=false implication (what happens if permission already exists?), side effects, or what the output schema contains.

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?

Single sentence of 9 words, front-loaded with the action verb. No redundant information, though extremely minimal to the point of omitting useful context about the permission model.

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?

Adequate for basic invocation given the comprehensive schema and existing output schema, but lacks explanation of the six permission levels' hierarchy, whether this appends or replaces permissions, and relationships to sibling permission tools.

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 adequately documents all three parameters (organization, user, permission). The description adds no additional parameter semantics (e.g., permission hierarchy explanation), 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 uses a specific verb ('Create') with clear resource ('permission') and scope ('for a user on an organization'). It effectively distinguishes from sibling tools like edubase_post_class_permission or edubase_post_course_permission by explicitly targeting 'organization'.

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?

No guidance provided on when to use this tool versus alternatives like edubase_get_organization_permission or edubase_delete_organization_permission. No mention of prerequisites (e.g., user/organization existence) or error conditions.

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