EduBase MCP Server

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

While annotations correctly indicate this is a non-destructive write operation, the description fails to explain what actually happens during the transfer (e.g., whether the previous owner loses access, if this affects existing members, or what the idempotentHint: false implies for repeated calls).

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 description is extremely terse (4 words), which avoids bloat, but it is under-specified rather than efficiently concise—every sentence must earn its place, and this single sentence merely restates the tool name without adding actionable detail.

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?

For a mutation operation involving organization ownership transfer, the description is inadequate. It omits critical context about side effects, authorization requirements, and the implications of the transfer, despite the existence of an output schema that could inform the agent of return structure.

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?

Schema description coverage is 100%, with both parameters documented as 'identification strings'. The description adds no further context about expected formats, valid ID patterns, or whether these refer to existing entities, 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 states the verb (transfer), resource (organization), and target (user), but 'transfer' is semantically ambiguous in this context—it does not clarify whether this changes ownership, administrative control, or membership, nor does it distinguish from sibling transfer tools like edubase_post_class_transfer or edubase_post_user_organizations.

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 (e.g., edubase_post_organization_members for adding users), nor any mention of prerequisites such as administrative permissions required to perform a transfer operation.

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